Potential Security Misconfiguration when Using withIssuerLocation
Spring Security
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-oauth2-jose Maven |
|
|
Spring Security
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-oauth2-jose Maven |
|
|
Vulnerability in Spring Spring Security. When an application configures JWT decoding with NimbusJwtDecoder or NimbusReactiveJwtDecoder, it must configure an OAuth2TokenValidator<Jwt> separately, for example by calling setJwtValidator.This issue affects Spring Security: from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.9, from 7.0.0 through 7.0.4.
From the CVE record · vmware
Applications using NimbusJwtDecoder or NimbusReactiveJwtDecoder must configure an OAuth2TokenValidator<Jwt> separately, such as by calling setJwtValidator. The input does not specify what an attacker can do, whether access is network or local, or whether authentication or user interaction is required.
Teams using Maven package org.springframework.security:spring-security-oauth2-jose should check versions 6.3.0–6.3.14, 6.4.0–6.4.14, 6.5.0–6.5.9, and 7.0.0–7.0.4.