Description
If Apache Pulsar is configured to authenticate clients using tokens based on JSON Web Tokens (JWT), the signature of the token is not validated if the algorithm of the presented token is set to "none". This allows an attacker to connect to Pulsar instances as any user (incl. admins).
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Apache Software Foundation | Apache Pulsar | Apache Pulsar – < 2.7.1 | 2.7.1 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Maven | org.apache.pulsar:pulsar | < 2.7.2 | 2.7.2 | GHSA-3cv4-xxv7-934q |
References
- https://lists.apache.org/thread.html/r347650d15a3e9c5f58b83e918b6ad6dedc2a63d3eb63da8e6a7be87e%40%3Cusers.pulsar.apache.org%3E
- [pulsar-dev] 20210527 Cutting 2.6.4 release to address CVE-2021-22160 mailing-list
- [pulsar-dev] 20210527 Re: [SECURITY] [CVE-2021-22160] Authentication with JWT allows use of "none"-algorithm mailing-list
- [pulsar-users] 20210527 Re: [SECURITY] [CVE-2021-22160] Authentication with JWT allows use of "none"-algorithm mailing-list
- [pulsar-dev] 20210527 Re: Cutting 2.6.4 release to address CVE-2021-22160 mailing-list
- Re: [SECURITY] [CVE-2021-22160] Authentication with JWT allows use of “none”-algorithm mailing-list
- [pulsar-dev] 20210531 Re: [DISCUSS] Propose More Formal Policy for Security Patches and EOL of Versions mailing-list
- [pulsar-dev] 20210604 Re: [DISCUSS] Propose More Formal Policy for Security Patches and EOL of Versions mailing-list