NVD / CVE Program· CNA apache

CVE-2024-27317: Apache Pulsar: Pulsar Functions Worker's Archive Extraction Vulnerability Allows Unauthorized File Modification

Noroxi assessment

Priority: Plan (action score 56/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: 56.9% (FIRST EPSS); higher than 99% 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 2.10.6, 2.11.4, 3.0.3.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to Apache Software Foundation Apache Pulsar 2.10.6, 2.11.4, 3.0.3 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

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.

CriticalCVSS 9.9 · v3.1—No exploit Fix available

Path traversal

Published: Mar 12, 2024
Updated: Jun 17, 2026
EPSS: 56.9% · 99th percentile
CWE: CWE-22

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 17 / 30 · 56.9%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 9.9
CNA · apache: 8.4; 1.5 point gap

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

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.

Running WordPress? Scan your site free with WP Lens

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.

Vendor	Product	CPE
apache	pulsar	cpe:2.3:a:apache:pulsar

Affected versions

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

apache pulsar2.4.0 and later · before 2.10.6
apache pulsar2.11.0 and later · before 2.11.4
apache pulsar3.0.0 and later · before 3.0.3
apache pulsar3.1.0 and later · before 3.1.3
apache pulsar3.2.0

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.4.0 and later · before 2.10.6affected · semver
- 2.11.0 and later · before 2.11.4affected · semver
- 3.0.0 and later · before 3.0.3affected · semver
- 3.1.0 and later · before 3.1.3affected · semver
- 3.2.0 and later · before 3.2.1affected · semver

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Maven	org.apache.pulsar:pulsar-functions-worker	from 2.11.0 · before 2.11.4	2.11.4
Maven	org.apache.pulsar:pulsar-functions-worker	from 2.4.0 · before 2.10.6	2.10.6
Maven	org.apache.pulsar:pulsar-functions-worker	from 3.0.0 · before 3.0.3	3.0.3
Maven	org.apache.pulsar:pulsar-functions-worker	from 3.1.0 · before 3.1.3	3.1.3
Maven	org.apache.pulsar:pulsar-functions-worker	from 3.2.0 · before 3.2.1	3.2.1

Same product

apache: all records

Other highest-scoring records for the same primary product.

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
CVE-2024-27894Apache Pulsar: Pulsar Functions Worker Allows Unauthorized File Access and Unauthorized HTTP/HTTPS Proxying
36Monitor

Published before and after this one in the same product

← EarlierCVE-2023-51437Feb 7, 2024 · Apache Pulsar: Timing attack in SASL token signature verification
29Monitor
← EarlierCVE-2022-34321Mar 12, 2024 · Apache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint
33Monitor
Later →CVE-2024-28098Mar 12, 2024 · Apache Pulsar: Improper Authorization For Topic-Level Policy Management
22Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Apache Software Foundation Apache Pulsar	2.10.6	Vendor (CNA)
Apache Software Foundation Apache Pulsar	2.11.4	Vendor (CNA)
Apache Software Foundation Apache Pulsar	3.0.3	Vendor (CNA)
Apache Software Foundation Apache Pulsar	3.1.3	Vendor (CNA)
Apache Software Foundation Apache Pulsar	3.2.1	Vendor (CNA)
Maven:org.apache.pulsar:pulsar-functions-worker	2.10.6	Package registry (OSV)
Maven:org.apache.pulsar:pulsar-functions-worker	2.11.4	Package registry (OSV)
Maven:org.apache.pulsar:pulsar-functions-worker	3.0.3	Package registry (OSV)
Maven:org.apache.pulsar:pulsar-functions-worker	3.1.3	Package registry (OSV)
Maven:org.apache.pulsar:pulsar-functions-worker	3.2.1	Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

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

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2022-343210 days apartApache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint
33Monitor
CVE-2023-3754483 days apartApache Pulsar WebSocket Proxy: Improper Authentication for WebSocket Proxy Endpoint Allows DoS
30Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0202 · Mar 14, 2024(Apache Güvenlik Zafiyeti)

All national notices →

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: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

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: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

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

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.openwall.com/lists/oss-security/2024/03/12/10

Show all references (2 more)

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

All records