cve.bz

CVE-2023-51437 apache pulsar: Observable Discrepancy

7.4 highEPSS 0.8%Fix available

High (7.4) in apache pulsar. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.pulsar:pulsar-broker-auth-sasl 2.11.3, 3.0.2, 3.1.1.

On this page
Observable timing discrepancy vulnerability in Apache Pulsar SASL Authentication Provider can allow an attacker to forge a SASL Role Token that will pass signature verification. Users are recommended to upgrade to version 2.11.3, 3.0.2, or 3.1.1 which fixes the issue. Users should also consider updating the configured secret in the `saslJaasServerRoleTokenSignerSecretPath` file. Any component matching an above version running the SASL Authentication Provider is affected. That includes the Pulsar Broker, Proxy, Websocket Proxy, or Function Worker. 2.11 Pulsar users should upgrade to at least 2.11.3. 3.0 Pulsar users should upgrade to at least 3.0.2. 3.1 Pulsar users should upgrade to at least 3.1.1. Any users running Pulsar 2.8, 2.9, 2.10, and earlier should upgrade to one of the above patched versions. For additional details on this attack vector, please refer to https://codahale.com/a-lesson-in-timing-attacks/ .

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 56th 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-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-203 Observable Discrepancy
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-51437 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-51437?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-51437?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-2023-51437 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 Pulsarthrough 2.10.5
Apache Software Foundation Apache Pulsarfrom 2.11.0 through 2.11.2
Apache Software Foundation Apache Pulsarfrom 3.0.0 through 3.0.1
Apache Software Foundation Apache Pulsar3.1.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c57v-4vg5-cm2xMavenorg.apache.pulsar:pulsar-broker-auth-sasl<2.11.32.11.3
GHSA-c57v-4vg5-cm2xMavenorg.apache.pulsar:pulsar-broker-auth-sasl>=3.0.0 <3.0.23.0.2
GHSA-c57v-4vg5-cm2xMavenorg.apache.pulsar:pulsar-broker-auth-sasl>=3.1.0 <3.1.13.1.1

Attack patterns (CAPEC)

  • CAPEC-189 Black Box Reverse Engineering Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON