dbcve.org
PulsarApplication · Apache

CVE-2024-27135

CRITICAL · 9.9 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 →
100/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
Improper input validation in the Pulsar Function Worker allows a malicious authenticated user to execute arbitrary Java code on the Pulsar Function worker, outside of the sandboxes designated for running user-provided functions. 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.

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

Improper input validation in Apache Pulsar Function Worker allows authenticated users to escape the sandbox and execute arbitrary Java code on the worker node itself. This also affects Pulsar Brokers with functionsWorkerEnabled=true, enabling remote code execution with worker-level privileges.

MitigationUpgrade to the patched versions (2.10.6+, 2.11.4+, 3.0.3+, 3.1.3+, 3.2.1+) or newer. If immediate upgrade is not possible, restrict Function Worker access to trusted authenticated users only and monitor for suspicious function submissions.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 Function Worker is enabled
    Check if the Pulsar Function Worker service is running. For standalone, look for the functions worker port (usually 8080 or 8443). For broker deployments, examine conf/broker.conf or conf/broker.yaml for functionsWorkerEnabled=true, or run: grep -r 'functionsWorkerEnabled' /path/to/pulsar/conf/
    Affected if Function Worker is enabled (standalone or via functionsWorkerEnabled=true in broker config)
  2. Identify the installed Pulsar version
    Run the Pulsar admin CLI: pulsar-admin versions or pulsar version. Alternatively, check the JAR files in the pulsar directory: ls -la pulsar-home/lib/ | grep pulsar
    Affected if Version matches: >= 2.4.0 and < 2.10.6, OR >= 2.11.0 and < 2.11.4, OR >= 3.0.0 and < 3.0.3, OR >= 3.1.0 and < 3.1.3, OR exactly 3.2.0
  3. Verify the Function Worker is network accessible
    Check if the Function Worker REST API port is exposed. Look for webServicePort or webServicePortTLS in conf/broker.conf (for embedded worker) or conf/functions_worker.yml (for standalone worker). Confirm with: curl -s http://worker-host:8080/admin/v2/tenants or similar admin endpoint responds
    Affected if Function Worker REST API is accessible over the network
  4. Check for function submission activity
    Review Pulsar function submission logs for recent user activity. Look in logs/pulsar-functions.log or logs/functions-worker.log for entries containing 'createFunction' or 'updateFunction' operations, especially from untrusted users
    Affected if Any function submissions have been made by non-admin or untrusted users since deployment

Environment is affected if Function Worker is enabled and the Pulsar version falls within the affected ranges listed above.

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 to the patched versions (2.10.6+, 2.11.4+, 3.0.3+, 3.1.3+, 3.2.1+) or newer. If immediate upgrade is not possible, restrict Function Worker access to trusted authenticated users only and monitor for suspicious function submissions.

Recommended fix High confidence

Upgrade to 2.10.6+ (2.10.x branch), 2.11.4+ (2.11.x branch), 3.0.3+ (3.0.x branch), 3.1.3+ (3.1.x branch), or 3.2.1+ (3.2.x branch) depending on current version branch

  1. Identify the current Apache Pulsar version deployed in the environment by checking the broker and function worker configurations
  2. Determine whether the Pulsar Broker has functionsWorkerEnabled=true or if a standalone Pulsar Function Worker is in use
  3. For Pulsar 2.10.x deployments: upgrade to version 2.10.6 or later (preferably the latest 2.10.x release)
  4. For Pulsar 2.11.x deployments: upgrade to version 2.11.4 or later (preferably the latest 2.11.x release)
  5. For Pulsar 3.0.x deployments: upgrade to version 3.0.3 or later (preferably the latest 3.0.x release)
  6. For Pulsar 3.1.x deployments: upgrade to version 3.1.3 or later (preferably the latest 3.1.x release)
  7. For Pulsar 3.2.x deployments: upgrade to version 3.2.1 or later (preferably the latest 3.2.x release)
  8. Test the upgrade in a non-production environment to verify functionality before deploying to production
Caveat Standard Pulsar upgrade considerations apply: review release notes for any breaking changes between versions, test function compatibility with new runtime, and plan for brief service downtime during upgrade

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27135 — 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-27135 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