CVE-2023-51437: Apache Pulsar: Timing attack in SASL token signature verification
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/ .
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-51437?
CVE-2023-51437 is classified as a significant security vulnerability due to its potential to allow SASL Role Token forgery.
How do I fix CVE-2023-51437?
To address the CVE-2023-51437 vulnerability, upgrade Apache Pulsar to version 2.11.3, 3.0.2, or 3.1.1.
What software is affected by CVE-2023-51437?
CVE-2023-51437 affects various versions of Apache Pulsar's SASL Authentication Provider, particularly versions prior to 2.11.3 and 3.1.1.
What does CVE-2023-51437 vulnerability allow an attacker to do?
CVE-2023-51437 allows an attacker to forge a SASL Role Token that may bypass signature verification.
Is there a patch available for CVE-2023-51437?
Yes, patches for CVE-2023-51437 are available in Apache Pulsar versions 2.11.3, 3.0.2, and 3.1.1.