Skip to content
Noroxi
NVD / CVE Program· CNA apache

CVE-2024-29834: Apache Pulsar: Improper Authorization For Namespace and Topic Management Endpoints

MediumCVSS 6.4 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 25/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 72% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Apache Software Foundation Apache Pulsar 3.0.4, 3.2.2.

Low priority for now. Upgrade to Apache Software Foundation Apache Pulsar 3.0.4, 3.2.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

This vulnerability allows authenticated users with produce or consume permissions to perform unauthorized operations on partitioned topics, such as unloading topics and triggering compaction. These management operations should be restricted to users with the tenant admin role or superuser role. An authenticated user with produce permission can create subscriptions and update subscription properties on partitioned topics, even though this should be limited to users with consume permissions. This impact analysis assumes that Pulsar has been configured with the default authorization provider. For custom authorization providers, the impact could be slightly different. Additionally, the vulnerability allows an authenticated user to read, create, modify, and delete namespace properties in any namespace in any tenant. In Pulsar, namespace properties are reserved for user provided metadata about the namespace. This issue affects Apache Pulsar versions from 2.7.1 to 2.10.6, from 2.11.0 to 2.11.4, from 3.0.0 to 3.0.3, from 3.1.0 to 3.1.3, and from 3.2.0 to 3.2.1. 3.0 Apache Pulsar users should upgrade to at least 3.0.4. 3.1 and 3.2 Apache Pulsar users should upgrade to at least 3.2.2. Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions.

Published
Apr 2, 2024
Updated
Jun 17, 2026
EPSS
1.3% · 72th percentile

Report tools

JSON

Action score

25

Monitor

Low priority for now.

CVSS
25 / 40 · 6.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.4
CNA · apache
6.4
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-29834

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for apache records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachepulsar

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Pulsar

    • 2.7.1 and later · up to and including 2.10.6affected · semver
    • 2.11.0 and later · up to and including 2.11.4affected · semver
    • 3.0.0 and later · before 3.0.4affected · semver
    • 3.1.0 and later · up to and including 3.1.3affected · semver
    • 3.2.0 and later · before 3.2.2affected · semver
Affected versions · NVD (5)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache pulsar2.7.1 and later · up to 2.10.6 inclusive
  • apache pulsar2.11.0 and later · up to 2.11.4 inclusive
  • apache pulsar3.0.0 and later · before 3.0.4
  • apache pulsar3.1.0 and later · up to 3.1.3 inclusive
  • apache pulsar3.2.0 and later · before 3.2.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.apache.pulsar:pulsar-brokerfrom 2.11.0 · up to and including 2.11.4—
Mavenorg.apache.pulsar:pulsar-brokerfrom 2.7.1 · up to and including 2.10.6—
Mavenorg.apache.pulsar:pulsar-brokerfrom 3.0.0 · before 3.0.43.0.4
Mavenorg.apache.pulsar:pulsar-brokerfrom 3.1.0 · up to and including 3.1.3—
Mavenorg.apache.pulsar:pulsar-brokerfrom 3.2.0 · before 3.2.23.2.2

Same product

apache: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-27317Apache Pulsar: Pulsar Functions Worker's Archive Extraction Vulnerability Allows Unauthorized File Modification
    56Plan
  • CVE-2021-22160Authentication with JWT allows use of “none”-algorithm
    55Plan
  • CVE-2024-27135Apache Pulsar: Improper Input Validation in Pulsar Function Worker allows Remote Code Execution
    41Plan

Published before and after this one in the same product

  • ← EarlierCVE-2024-27894Mar 12, 2024 · Apache Pulsar: Pulsar Functions Worker Allows Unauthorized File Access and Unauthorized HTTP/HTTPS Proxying
    36Monitor
  • ← EarlierCVE-2024-28098Mar 12, 2024 · Apache Pulsar: Improper Authorization For Topic-Level Policy Management
    22Monitor
  • Later →CVE-2025-30677Apr 9, 2025 · Apache Pulsar IO Kafka Connector, Apache Pulsar IO Kafka Connect Adaptor: Sensitive information logged in Pulsar's Apache Kafka Connectors
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Apache Software Foundation Apache Pulsar3.0.4Vendor (CNA)
Apache Software Foundation Apache Pulsar3.2.2Vendor (CNA)
Maven:org.apache.pulsar:pulsar-broker3.0.4Package registry (OSV)
Maven:org.apache.pulsar:pulsar-broker3.2.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-30429265 days apartApache Pulsar: Incorrect Authorization for Function Worker when using mTLS Authentication through Pulsar Proxy
    35Monitor
  • CVE-2023-30428265 days apartApache Pulsar Broker: Incorrect Authorization Validation for Rest Producer
    32Monitor
  • CVE-2023-37579265 days apartApache Pulsar Function Worker: Incorrect Authorization for Function Worker Can Leak Sink/Source Credentials
    26Monitor
  • CVE-2024-2809821 days apartApache Pulsar: Improper Authorization For Topic-Level Policy Management
    22Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records