GHSA-4gc7-5j7h-4qph is a medium-severity (CVSS 5.3) CWE-178 vulnerability in org.springframework:spring-context. O3 Security confirms whether GHSA-4gc7-5j7h-4qph is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spring Framework DataBinder Case Sensitive Match Exception
Real-World Exposure
org.springframework:spring-context☕org.springframework:spring-web☕org.springframework:spring-web☕org.springframework:spring-context☕org.springframework:spring-context☕org.springframework:spring-webReal-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
The fix for CVE-2022-22968 made disallowedFields patterns in DataBinder case insensitive. However, String.toLowerCase() has some Locale dependent exceptions that could potentially result in fields not protected as expected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-context | ≥ 6.1.0&&< 6.1.14 | 6.1.14 |
| ☕Maven | org.springframework:spring-web | ≥ 6.1.0&&< 6.1.14 | 6.1.14 |
| ☕Maven | org.springframework:spring-web | ≥ 6.0.0 | No fix |
| ☕Maven | org.springframework:spring-context | ≥ 6.0.0 | No fix |
| ☕Maven | org.springframework:spring-context | all versions | No fix |
| ☕Maven | org.springframework:spring-web | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-context. 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.
Fix
Update org.springframework:spring-context to 6.1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4gc7-5j7h-4qph is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-4gc7-5j7h-4qph 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-4gc7-5j7h-4qph. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4gc7-5j7h-4qph in your dependencies?
O3 detects GHSA-4gc7-5j7h-4qph across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.