dbcve.org
PulsarApplication · Apache

CVE-2024-27894

HIGH · 8.8 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 2.10.6 / 2.11.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Pulsar Functions Worker allows authenticated users to create functions from URLs supporting 'file', 'http', and 'https' schemes. The 'file://' scheme permits reading any file accessible to the Worker process, including environment variables containing secrets. Additionally, the HTTP/HTTPS schemes enable the Worker to be abused as a proxy for remote attacks or DoS.

MitigationUpgrade Pulsar to version 2.10.6+, 2.11.4+, 3.0.3+, 3.1.3+, or 3.2.1+. If the URL-based function feature is required, configure 'additionalEnabledConnectorUrlPatterns' and 'additionalEnabledFunctionsUrlPatterns' to whitelist specific permitted URL patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PulsarApplication
Affected:>= 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

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Functions Worker is enabled
    Check if the Pulsar Functions Worker service is running or if functionsWorkerEnabled is set to true in the broker.conf or functions_worker.yml configuration file
    Affected if Functions Worker is enabled and exposed to authenticated users
  2. Determine installed Pulsar version
    Run 'pulsar version' or check the pulsar-\(version\).jar file in the installation directory, or inspect the package version via your package manager
    Affected if Version falls within any of these ranges: >= 2.4.0 and < 2.10.6, >= 2.11.0 and < 2.11.4, >= 3.0.0 and < 3.0.3, >= 3.1.0 and < 3.1.3, or exactly 3.2.0
  3. Check if URL-based function creation is allowed
    Inspect the broker.conf or functions_worker.yml for the presence and configuration of 'additionalEnabledConnectorUrlPatterns' and 'additionalEnabledFunctionsUrlPatterns' settings. If these are absent or permit wildcards, the feature is unrestricted.
    Affected if No URL pattern restrictions are configured, or patterns allow arbitrary file://, http://, or https:// URLs
  4. Verify function creation API exposure
    Review Pulsar authentication and authorization settings to confirm which authenticated users can invoke the '/functions/create' API endpoint with URL-based function class paths
    Affected if Authenticated users have permission to create functions from arbitrary URLs

You are affected if Functions Worker is enabled, your Pulsar version is in the vulnerable ranges listed, and URL pattern restrictions (additionalEnabledFunctionsUrlPatterns or additionalEnabledConnectorUrlPatterns) are not configured to whitelist specific patterns.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.6 / 2.11.4 / 3.0.3 or later
Fixed in 2.10.62.11.43.0.3
Interim mitigation

Upgrade Pulsar to version 2.10.6+, 2.11.4+, 3.0.3+, 3.1.3+, or 3.2.1+. If the URL-based function feature is required, configure 'additionalEnabledConnectorUrlPatterns' and 'additionalEnabledFunctionsUrlPatterns' to whitelist specific permitted URL patterns.

Recommended fix High confidence

Upgrade to 2.10.6 (for 2.10.x branch), 2.11.4 (for 2.11.x branch), 3.0.3 (for 3.0.x branch), 3.1.3 (for 3.1.x branch), or 3.2.1 (for 3.2.x branch)

  1. 1. Identify the current Pulsar version in use by checking the installed Pulsar packages or container images
  2. 2. Determine the appropriate upgrade path based on current version: for 2.4.0-2.10.5 upgrade to 2.10.6; for 2.11.0-2.11.3 upgrade to 2.11.4; for 3.0.0-3.0.2 upgrade to 3.0.3; for 3.1.0-3.1.2 upgrade to 3.1.3; for 3.2.0 upgrade to 3.2.1
  3. 3. Stop the Pulsar Functions Worker or Broker service
  4. 4. Upgrade Pulsar to the target patched version using the package manager or by deploying the new container image
  5. 5. Start the Pulsar service and verify it is running correctly
  6. 6. If the URL-based function creation feature is required, configure additionalEnabledConnectorUrlPatterns and additionalEnabledFunctionsUrlPatterns in the functions worker config to specify permitted URL patterns
Caveat Default restrictions now block URL-based function creation; users must explicitly configure allowed URL patterns if this feature is needed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pulsar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-27894 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data