Critical · published July 12, 2023
🚨 A sneaky role mix-up is at play! Before version 2.10.4, Apache Pulsar mistakenly uses the Proxy's permissions instead of the client's, which could lead to privilege escalations as if a waiter suddenly gained a chef's authority! 🔥 Think of it like a restaurant where the cashier can give out discounts meant only for the head chef — a recipe for disaster when an unqualified cashier starts serving up superuser powers! An attacker could leverage this authorization slip-up to gain access and do nearly anything — from viewing sensitive data to performing actions that should be reserved solely for superusers. With this vulnerability, your entire system's integrity could be compromised!
Think of it like a restaurant where the cashier can give out discounts meant only for the head chef — a recipe for disaster when an unqualified cashier starts serving up superuser powers! This issue arises because the Pulsar Function Worker incorrectly authorizes client requests by checking the Proxy's role instead of the client's role, allowing for unintended privilege escalation.
An attacker could leverage this authorization slip-up to gain access and do nearly anything — from viewing sensitive data to performing actions that should be reserved solely for superusers. With this vulnerability, your entire system's integrity could be compromised! Upgrade your Pulsar Function Worker to at least version 2.10.4 if you're on the 2.10 series, or to at least 2.11.1 for the 2.11 series. Users on 2.9.* and earlier should also upgrade to one of these patched versions to maintain security! You've got this! Follow these steps, and you'll reinforce your defenses in no time! 🛡️