Home
» GitHub Advisories
» GHSA-6gf2-pvqw-37ph
Description
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.
Basic information
Type
reviewed
Severity
medium Advisory on GitHub
Open advisory ↗ Repository advisory
—
Source code
Not specified Published (advisory)
2022-01-12 23:04:06 UTC
Updated
2023-02-03 05:04:29 UTC
GitHub reviewed
2022-01-11 18:50:39 UTC
NVD published
2022-01-10
EPSS Score
Score
Percentile
0.16%
37.17%
CVSS Scores
Base score
Version
Severity
Vector
4.3
3.1
—
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
Affected packages (2)
Vulnerable version ranges and first patched releases as published by GitHub.
Ecosystem
Package
Vulnerable range
First patched
Vulnerable functions
maven
org.springframework:spring-core >= 5.3.0, < 5.3.14
5.3.14
—
maven
org.springframework:spring-core >= 5.2.0, < 5.2.19
5.2.19
—
cvelogic
Threat Intelligence