cve.bz

CVE-2024-27894 apache pulsar: Improper Input Validation

8.8 highEPSS 1.9%Fix available

High (8.8) in apache pulsar. EPSS 1.9% 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
The Pulsar Functions Worker includes a capability that permits authenticated users to create functions where the function's implementation is referenced by a URL. The supported URL schemes include "file", "http", and "https". When a function is created using this method, the Functions Worker will retrieve the implementation from the URL provided by the user. However, this feature introduces a vulnerability that can be exploited by an attacker to gain unauthorized access to any file that the Pulsar Functions Worker process has permissions to read. This includes reading the process environment which potentially includes sensitive information, such as secrets. Furthermore, an attacker could leverage this vulnerability to use the Pulsar Functions Worker as a proxy to access the content of remote HTTP and HTTPS endpoint URLs. This could also be used to carry out denial of service attacks. 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. The updated versions of Pulsar Functions Worker will, by default, impose restrictions on the creation of functions using URLs. For users who rely on this functionality, the Function Worker configuration provides two configuration keys: "additionalEnabledConnectorUrlPatterns" and "additionalEnabledFunctionsUrlPatterns". These keys allow users to specify a set of URL patterns that are permitted, enabling the creation of functions using URLs that match the defined patterns. This approach ensures that the feature remains available to those who require it, while limiting the potential for unauthorized access and exploitation.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.9% (unchanged from 1.9% a week ago; 1.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 80th 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: partial, assessed 2024-03-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-552 Files or Directories Accessible to External Parties
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
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-27894 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-27894?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-27894?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-27894 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-c2x9-vw5h-39vcMavenorg.apache.pulsar:pulsar-functions-worker>=2.4.0 <2.10.62.10.6
GHSA-c2x9-vw5h-39vcMavenorg.apache.pulsar:pulsar-functions-worker>=2.11.0 <2.11.42.11.4
GHSA-c2x9-vw5h-39vcMavenorg.apache.pulsar:pulsar-functions-worker>=3.0.0 <3.0.33.0.3
GHSA-c2x9-vw5h-39vcMavenorg.apache.pulsar:pulsar-functions-worker>=3.1.0 <3.1.33.1.3
GHSA-c2x9-vw5h-39vcMavenorg.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-pulsarNot affected
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-27894.

Attack patterns (CAPEC)

  • CAPEC-150 Collect Data from Common Resource Locations Severity: Medium
  • CAPEC-639 Probe System Files Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON