Log entry injection in Spring Framework
Published 12 Jan 2022 · Updated 4 Dec 2024
Is your project on an affected org.springframework:spring-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=5.3.0 <5.3.14
- Fixed in
- 5.3.14
mvn versions:use-dep-version -Dincludes=org.springframework:spring-core -DdepVersion=5.3.14 -DforceVersion=true- Affected
- >=5.2.0 <5.2.19
- Fixed in
- 5.2.19
mvn versions:use-dep-version -Dincludes=org.springframework:spring-core -DdepVersion=5.2.19 -DforceVersion=trueDetails
In Spring Framework versions 5.3.0 - 5.3.13, 5.2.0 - 5.2.18, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries. This is a follow-up to CVE-2021-22096 that protects against additional types of input and in more places of the Spring Framework codebase.
Is GHSA-6gf2-pvqw-37ph in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.springframework:spring-core, and gives you the command that fixes it.
More advisories for org.springframework:spring-core
- LowCVE-2026-41848Spring Framework Denial of Service via AntPathMatcher · 9 Jun 2026
- HighCVE-2025-41249Spring Framework annotation detection mechanism may result in improper authorization · 16 Sept 2025
- HighCVE-2024-22233Spring Framework server Web DoS Vulnerability · 22 Jan 2024
- MediumCVE-2021-22096Improper Output Neutralization for Logs in Spring Framework · 24 May 2022
- HighCVE-2011-2730Improper Neutralization of Directives in Dynamically Evaluated Code in Spring Framework · 17 May 2022
- MediumCVE-2011-2894Spring Framework and Spring Security vulnerable to Deserialization of Untrusted Data · 14 May 2022
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.