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.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Micronaut_security | Objectcomputing | * | 3.1.2 (excluding) |
| Micronaut_security | Objectcomputing | 3.2.0 (including) | 3.2.4 (excluding) |
| Micronaut_security | Objectcomputing | 3.3.0 (including) | 3.3.2 (excluding) |
| Micronaut_security | Objectcomputing | 3.4.0 (including) | 3.4.3 (excluding) |
| Micronaut_security | Objectcomputing | 3.5.0 (including) | 3.5.3 (excluding) |
| Micronaut_security | Objectcomputing | 3.6.0 (including) | 3.6.6 (excluding) |
| Micronaut_security | Objectcomputing | 3.7.0 (including) | 3.7.4 (excluding) |
| Micronaut_security | Objectcomputing | 3.8.0 (including) | 3.8.4 (excluding) |
| Micronaut_security | Objectcomputing | 3.9.0 (including) | 3.9.6 (excluding) |
| Micronaut_security | Objectcomputing | 3.10.0 (including) | 3.10.2 (excluding) |
| Micronaut_security | Objectcomputing | 3.11.0 (including) | 3.11.0 (including) |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: