CVE-2024-27894
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
Apache Pulsar: Pulsar Functions Worker Allows Unauthorized File Access and Unauthorized HTTP/HTTPS Proxying
rank 28 = 0 + 22 + 0 + 6 + 0
rank@v1 · scheduled
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.01895 · without this subject the record ranks 28
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 8.8, from NVD · without this subject the record ranks 6
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
no persisting rise in 365 days · without this subject the record ranks 28
How much of the world it touches
NVD CPE configurations
5 products in the CPE ranges · without this subject the record ranks 22
Someone else already set the date
CISA KEV remediation due date
no CISA due date · without this subject the record ranks 28
$94,600 = $4.99M incident cost x 1 exposure x 0.01895 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
Hindsight · the state
Foresight · where to check next
This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1
Sources disagree here.
Both shown, dated. We don't pick winners. disagreement-rules@v1
Running Apache Pulsar? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Set up a watchlist (needs a Practitioner account)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
AcceptDeferPatch by…Not affectedMitigatedChoose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Nothing observed in held sources.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published
- RUNG 3Exploited in the wild · CISA KEV listed
- RUNG 4Ransomware campaign use known
Affected & Fixed Versions as published
Show all 5 published ranges
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
Attack path
What it is stated by the CNA
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. receipt
Read the rest of the CNA's description
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.
NVD's analysis a second authority
- severity
- 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- weakness
- CWE-20; CWE-552
- affected versions
- apache pulsar >= 2.4.0 < 2.10.6; apache pulsar >= 2.11.0 < 2.11.4; apache pulsar >= 3.0.0 < 3.0.3; and 2 more, listed in full below
- also scored by
- [email protected] 8.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
The CNA scored it 8.5 and NVD 8.8. Both are shown because both were published; we do not pick one.
check it yourself lists.apache.org pulsar.apache.org openwall.com receipt
Movement the material steps
Show all 17 observations
17 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The full biography
The record had been public for 2 years, 3 months when this index was last written.
The pattern, elsewhere
This record is one instance of CWE-20, improper input validation. The index holds 13347 prior instances of this class, 73 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]
"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1
13347 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.
No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.
Siblings and hubs
Records related to this one
No record cites this identifier and it carries no alias. Its defect family is below.
Its defect family
apache software foundation apache pulsar
Of the 3 records in this family, this is the only one whose title names functions unauthorized file.
Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.
Family membership: held values
This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.
Browse the index from here
These are index-wide views, not findings about CVE-2024-27894.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.