Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-6gf2-pvqw-37ph

MEDIUM

GHSA-6gf2-pvqw-37ph is a medium-severity (CVSS 4.3) vulnerability in org.springframework:spring-core. O3 Security confirms whether GHSA-6gf2-pvqw-37ph is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Log entry injection in Spring Framework

Also known asCVE-2021-22060
Published
Jan 12, 2022
Updated
Dec 4, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
org.springframework:spring-coreorg.springframework:spring-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.springframework:spring-core5.3.0&&< 5.3.145.3.14
Mavenorg.springframework:spring-core5.2.0&&< 5.2.195.2.19

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.springframework:spring-core to 5.3.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6gf2-pvqw-37ph is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-6gf2-pvqw-37ph is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6gf2-pvqw-37ph. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-6gf2-pvqw-37ph in your dependencies?

O3 detects GHSA-6gf2-pvqw-37ph across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.