cve.bz

CVE-2024-27317 apache pulsar: Path traversal

9.9 criticalEPSS 57%Fix available

Critical (9.9) in apache pulsar. EPSS 57% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.pulsar:pulsar-functions-worker 2.10.6, 2.11.4, 3.0.3.

On this page
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.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
57% (unchanged from 57% a week ago; 57% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-08-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-27317 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-27317?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-27317?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-27317 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Pulsarfrom 2.4.0 before 2.10.6
Apache Software Foundation Apache Pulsarfrom 2.11.0 before 2.11.4
Apache Software Foundation Apache Pulsarfrom 3.0.0 before 3.0.3
Apache Software Foundation Apache Pulsarfrom 3.1.0 before 3.1.3
Apache Software Foundation Apache Pulsarfrom 3.2.0 before 3.2.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jg2g-4rjg-cmqhMavenorg.apache.pulsar:pulsar-functions-worker>=2.4.0 <2.10.62.10.6
GHSA-jg2g-4rjg-cmqhMavenorg.apache.pulsar:pulsar-functions-worker>=2.11.0 <2.11.42.11.4
GHSA-jg2g-4rjg-cmqhMavenorg.apache.pulsar:pulsar-functions-worker>=3.0.0 <3.0.33.0.3
GHSA-jg2g-4rjg-cmqhMavenorg.apache.pulsar:pulsar-functions-worker>=3.1.0 <3.1.33.1.3
GHSA-jg2g-4rjg-cmqhMavenorg.apache.pulsar:pulsar-functions-worker>=3.2.0 <3.2.13.2.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

Apache Pulsar is not part of EAP - it's not present in the EAP dependency tree and not distributed in the product maven repository. EAP is not affected.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat build of Apache Camel for Spring Boot 3apache-pulsarNot affected
Red Hat build of Apache Camel for Spring Boot 4apache-pulsarNot affected
Red Hat Fuse 7apache-pulsarWill not fix
Red Hat Integration Camel K 1apache-pulsarNot affected
Red Hat JBoss Enterprise Application Platform 8apache-pulsarNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-27317.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON