CVE-2023-51437
Last modified
CVE-2023-51437 is a high-severity vulnerability rated 7.4/10 on the CVSS scale. 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. EPSS estimates a 0.76% chance of exploitation in the next 30 days.
Description
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/ .
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Pulsar | <= 2.10.5 |
| Apache | Pulsar | >= 2.11.0, < 2.11.3 |
| Apache | Pulsar | >= 3.0.0, < 3.0.2 |
| Apache | Pulsar | 3.1.0 |
References
- https://lists.apache.org/thread/5kgmvvolf5tzp5rz9xjwfg2ncwvqqgl5Issue Tracking, Vendor Advisory
- https://lists.apache.org/thread/5kgmvvolf5tzp5rz9xjwfg2ncwvqqgl5Issue Tracking, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-51437?
How severe is CVE-2023-51437?
How do I fix CVE-2023-51437?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-51431 Some Honor products are affected by incorrect privilege ass…5.5
- CVE-2023-51432 Some Honor products are affected by out of bounds read vuln…5.5
- CVE-2023-51433 Some Honor products are affected by incorrect privilege ass…5.5
- CVE-2023-51434 Some Honor products are affected by buffer overflow vulnera…7.8
- CVE-2023-51435 Some Honor products are affected by incorrect privilege ass…7.1
- CVE-2023-51436Cross-site scripting vulnerability exists in UNIVERSAL PASSP…5.9
- CVE-2023-51438A vulnerability has been identified in SIMATIC IPC1047E (All…9.8
- CVE-2023-51439A vulnerability has been identified in JT2Go (All versions <…7.8
- CVE-2023-5144** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was c…8.8
- CVE-2023-51440A vulnerability has been identified in SIMATIC CP 343-1 (6GK…7.5
- CVE-2023-51441** UNSUPPORTED WHEN ASSIGNED ** Improper Input Validation vu…7.2
- CVE-2023-51442Navidrome is an open source web-based music collection serve…8.6
Are you affected by CVE-2023-51437?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
