micronaut security has invalid IdTokenClaimsValidator logic on aud
micronaut-projects micronaut-security
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.micronaut.security:micronaut-security-oauth2 Maven |
|
micronaut-projects micronaut-security
| Product | Affected | Fixed in |
|---|---|---|
| io.micronaut.security:micronaut-security-oauth2 Maven |
|
≥ 3.3.0 · < 3.3.2≥ 3.2.0 · < 3.2.4≥ 3.1.0 · < 3.1.2
|
Micronaut Security is a security solution for applications. Prior to versions 3.1.2, 3.2.4, 3.3.2, 3.4.3, 3.5.3, 3.6.6, 3.7.4, 3.8.4, 3.9.6, 3.10.2, and 3.11.1, IdTokenClaimsValidator skips `aud` claim validation if token is issued by same identity issuer/provider. Any OIDC setup using Micronaut where multiple OIDC applications exists for the same issuer but token auth are not meant to be shared. This issue has been patched in versions 3.1.2, 3.2.4, 3.3.2, 3.4.3, 3.5.3, 3.6.6, 3.7.4, 3.8.4, 3.9.6, 3.10.2, and 3.11.1.
From the CVE record · GitHub_M
IdTokenClaimsValidator skips `aud` claim validation for tokens issued by the same identity provider. In an OIDC setup with multiple applications sharing an issuer but not intended to share token authentication, a token for one application may be accepted by another. The input does not specify any user interaction requirement.
Teams using Maven io.micronaut.security:micronaut-security-oauth2 should check versions >=3.1.0 <3.1.2, >=3.2.0 <3.2.4, >=3.3.0 <3.3.2, >=3.4.0 <3.4.3, >=3.5.0 <3.5.3, >=3.6.0 <3.6.6, >=3.7.0 <3.7.4, >=3.8.0 <3.8.4, >=3.9.0 <3.9.6, >=3.10.0 <3.10.2, or >=3.11.0 <3.11.1.