Impacted versions:
- Confluent Platform <= 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3 brokers that use SASL/OAUTHBEARER with a JWKS endpoint configured (the default JWT validator)
Recommended action:
- Set both the expected issuer and the audience on every OAUTHBEARER listener (see Remediation).
- Upgrade to Confluent Platform 8.4.0 or later to enforce the audience and issuer checks.
Issue:
A security vulnerability has been identified in the Apache Kafka JWT validator. The broker JWT validator (BrokerJwtValidator) checks the issuer and audience claims of a token only when expected values are configured. If they are not set, a token that is otherwise valid, for example one signed by the same identity provider but issued for a different application, could be accepted by the broker. As a result, a principal that holds a token intended for another service could authenticate to the Kafka broker, resulting in loss of confidentiality, integrity and availability.
Mitigation:
Every broker listener that uses SASL/OAUTHBEARER with a JWKS endpoint, needs the following two properties configured:
- sasl.oauthbearer.expected.issuer: the iss value your identity provider puts in tokens meant for Kafka.
- sasl.oauthbearer.expected.audience: the aud value(s) your identity provider puts in tokens meant for Kafka.
If OAUTHBEARER is configured per listener, use the listener-prefixed form of each property.
Confluent Platform 8.4.0 fully resolves this issue by enforcing the above mitigation. If the above configurations are not set, the broker will fail to start. If you deliberately do not want to restrict the issuer or the audience, you can set sasl.oauthbearer.allow.unverified.issuer=true or sasl.oauthbearer.allow.unverified.audience=true. Both default to false, and the broker logs a warning at startup when either is enabled. Leaving a check off keeps the original exposure for that check.
CVSS Scores:
Original CVSS : 5.9
-
Confluent Platform: 6.4 (CVSS v3.1 Calculator)