Skip to content
Fencer Vulns
high 8.4

CVE-2024-27317 in the critical feed json

Apache Pulsar: Pulsar Functions Worker's Archive Extraction Vulnerability Allows Unauthorized File Modification

published 2024-03-12 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-0948 , GHSA-jg2g-4rjg-cmqh

cvss
8.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
56.9%
EPSS 56.9% chance of exploitation in 30 days, percentile 99%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.pulsar:pulsar-functions-worker 2.10.6, 2.11.4, 3.0.3, 3.1.3, 3.2.1
  • Apache Software Foundation Apache Pulsar 2.10.6, 2.11.4, 3.0.3, 3.1.3, 3.2.1
  • apache pulsar 2.10.6, 2.11.4, 3.0.3, 3.1.3, 3.2.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-27317 updated cvss 8.4

apache-pulsar: Pulsar Functions Worker's Archive Extraction Vulnerability Allows Unauthorized File Modification

  • Red Hat Fuse 7 apache-pulsar apache-pulsar
    affected: workaround, no fix planned “Will not fix”
  • Red Hat build of Apache Camel for Spring Boot 3 apache-pulsar apache-pulsar Red Hat build of Apache Camel for Spring Boot 4 apache-pulsar apache-pulsar Red Hat Integration Camel K 1 apache-pulsar apache-pulsar Red Hat JBoss Enterprise Application Platform 8 apache-pulsar apache-pulsar
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

56.93% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.pulsar:pulsar-functions-worker
>=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, <3.2.1
2.10.6
2.11.4
3.0.3
3.1.3
3.2.1

Affected products

  • Apache Software Foundation Apache Pulsar
  • apache pulsar

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.