dbcve.org
PulsarApplication · Apache

CVE-2024-27317

CRITICAL · 9.9 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 2.10.6 / 2.11.4 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Pulsar Functions Worker, authenticated users can upload functions in jar or nar files. These files, essentially zip files, are extracted by the Functions Worker. However, if a malicious file is uploaded, it could exploit a directory traversal vulnerability. This occurs when the filenames in the zip files, which aren't properly validated, contain special elements like "..", altering the directory path. This could allow an attacker to create or modify files outside of the designated extraction directory, potentially influencing system behavior. This vulnerability also applies to the Pulsar Broker when it is configured with "functionsWorkerEnabled=true". This issue affects Apache Pulsar versions from 2.4.0 to 2.10.5, from 2.11.0 to 2.11.3, from 3.0.0 to 3.0.2, from 3.1.0 to 3.1.2, and 3.2.0. 2.10 Pulsar Function Worker users should upgrade to at least 2.10.6. 2.11 Pulsar Function Worker users should upgrade to at least 2.11.4. 3.0 Pulsar Function Worker users should upgrade to at least 3.0.3. 3.1 Pulsar Function Worker users should upgrade to at least 3.1.3. 3.2 Pulsar Function Worker users should upgrade to at least 3.2.1. Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Directory traversal vulnerability in Apache Pulsar Functions Worker allows authenticated users to upload malicious jar/nar files (zip archives) containing filenames with '..' path traversal sequences. When extracted, these files can write to arbitrary locations outside the designated extraction directory, enabling potential system compromise. The vulnerability also affects Pulsar Broker when configured with functionsWorkerEnabled=true.

MitigationUpgrade Apache Pulsar to patched versions (2.10.6+, 2.11.4+, 3.0.3+, 3.1.3+, or 3.2.1+) to resolve the improper filename validation in zip extraction.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PulsarApplication
Affected:>= 2.4.0, < 2.10.6>= 2.11.0, < 2.11.4>= 3.0.0, < 3.0.3>= 3.1.0, < 3.1.3= 3.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Pulsar version
    Run `bin/pulsar version` or check the version field in `lib/pulsar-common-[version].jar` manifest, or check the RPM/deb package version
    Affected if The version falls within: >= 2.4.0 and < 2.10.6; OR >= 2.11.0 and < 2.11.4; OR >= 3.0.0 and < 3.0.3; OR >= 3.1.0 and < 3.1.3; OR exactly 3.2.0
  2. Check if Functions Worker is enabled in Broker
    Inspect the broker configuration file (typically `conf/broker.conf` or `conf/broker.conf`) and look for the setting `functionsWorkerEnabled`
    Affected if The setting `functionsWorkerEnabled` is set to `true` in the broker configuration
  3. Check if standalone Functions Worker is in use
    Inspect the standalone configuration file (`conf/standalone.conf`) and look for whether Functions Worker settings are configured, or check if Pulsar is running in standalone mode with functions enabled
    Affected if Pulsar is running in standalone mode with Functions Worker active

You are affected if your Pulsar version is in the affected ranges AND Functions Worker is enabled (either via broker.conf with functionsWorkerEnabled=true or in standalone mode).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.6 / 2.11.4 / 3.0.3 or later
Fixed in 2.10.62.11.43.0.3
Interim mitigation

Upgrade Apache Pulsar to patched versions (2.10.6+, 2.11.4+, 3.0.3+, 3.1.3+, or 3.2.1+) to resolve the improper filename validation in zip extraction.

Recommended fix High confidence

Upgrade to 2.10.6+, 2.11.4+, 3.0.3+, 3.1.3+, or 3.2.1+ depending on your current version branch

  1. 1. Identify the currently running Apache Pulsar version using pulsar-admin or broker logs.
  2. 2. Determine which version branch you are on (2.10.x, 2.11.x, 3.0.x, 3.1.x, or 3.2.x).
  3. 3. For version 2.10.x: upgrade Pulsar to version 2.10.6 or later.
  4. 4. For version 2.11.x: upgrade Pulsar to version 2.11.4 or later.
  5. 5. For version 3.0.x: upgrade Pulsar to version 3.0.3 or later.
  6. 6. For version 3.1.x: upgrade Pulsar to version 3.1.3 or later.
  7. 7. For version 3.2.x: upgrade Pulsar to version 3.2.1 or later.
  8. 8. After upgrade, verify that functionsWorkerEnabled configuration is set appropriately for your deployment.
Caveat Review release notes for any breaking changes between your current version and target version; major version upgrades may require configuration or API adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pulsar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-27317 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data