First published: Mon Mar 03 2025(Updated: )
In certain IETF OAuth 2.0-related specifications, when the JSON Web Token Profile for OAuth 2.0 Client Authentication mechanism is used, there are ambiguities in the audience values of JWTs sent to authorization servers. The affected RFCs may include RFC 7523, and also RFC 7521, RFC 7522, RFC 9101 (JAR), and RFC 9126 (PAR).
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
IETF RFC 7523 | ||
IETF RFC 7521 | ||
RFC 7522 | ||
RFC 9101 | ||
IETF RFC 9126 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-27371 has been classified with a moderate severity level due to ambiguities in audience values of JWTs.
To fix CVE-2025-27371, ensure that the audience values of JWTs conform to clear and well-defined specifications outlined in the affected RFCs.
CVE-2025-27371 affects implementations using certain IETF RFCs, specifically RFC 7523, RFC 7522, and RFC 9101.
The potential impacts of CVE-2025-27371 include unauthorized access due to improper audience validation in token handling.
As of now, there are no official workarounds for CVE-2025-27371 other than adhering to the proper configurations as per the relevant RFC specifications.