Apache Pulsar: Timing attack in SASL token signature verification
Apache Software Foundation Apache Pulsar
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.pulsar:pulsar-broker-auth-sasl Maven |
|
|
Apache Software Foundation Apache Pulsar
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.pulsar:pulsar-broker-auth-sasl Maven |
|
|
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/ .
From the CVE record · apache
An observable timing discrepancy in the Apache Pulsar SASL Authentication Provider can let an attacker forge a SASL Role Token that passes signature verification. This affects vulnerable Broker, Proxy, Websocket Proxy, or Function Worker components running the provider. The input does not specify network access, authentication, or user-interaction requirements.
Operators running the SASL Authentication Provider should check Pulsar versions before 2.11.3, 3.0.0 through 3.0.1, or 3.1.0, including earlier 2.8–2.10 releases.