Summary
Apache Pulsar: Pulsar Functions Worker's Archive Extraction Vulnerability Allows Unauthorized File Modification
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.
Impact
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
CVE-2024-27317 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.10.6, 2.11.4, 3.0.3, 3.1.3, 3.2.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.pulsar:pulsar-functions-worker to 2.10.6 or later; org.apache.pulsar:pulsar-functions-worker to 2.11.4 or later; org.apache.pulsar:pulsar-functions-worker to 3.0.3 or later; org.apache.pulsar:pulsar-functions-worker to 3.1.3 or later; org.apache.pulsar:pulsar-functions-worker to 3.2.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-27317? CVE-2024-27317 is a critical-severity path traversal vulnerability in org.apache.pulsar:pulsar-functions-worker (maven), affecting versions >= 2.4.0, < 2.10.6. It is fixed in 2.10.6, 2.11.4, 3.0.3, 3.1.3, 3.2.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- How severe is CVE-2024-27317? CVE-2024-27317 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.apache.pulsar:pulsar-functions-worker are affected by CVE-2024-27317? org.apache.pulsar:pulsar-functions-worker (maven) versions >= 2.4.0, < 2.10.6 is affected.
- Is there a fix for CVE-2024-27317? Yes. CVE-2024-27317 is fixed in 2.10.6, 2.11.4, 3.0.3, 3.1.3, 3.2.1. Upgrade to this version or later.
- Is CVE-2024-27317 exploitable, and should I be worried? Whether CVE-2024-27317 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-27317 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-27317?
- Upgrade
org.apache.pulsar:pulsar-functions-workerto 2.10.6 or later - Upgrade
org.apache.pulsar:pulsar-functions-workerto 2.11.4 or later - Upgrade
org.apache.pulsar:pulsar-functions-workerto 3.0.3 or later - Upgrade
org.apache.pulsar:pulsar-functions-workerto 3.1.3 or later - Upgrade
org.apache.pulsar:pulsar-functions-workerto 3.2.1 or later
- Upgrade