How severe is GHSA-rhcg-rwhx-qj3j?

No CVSS score has been assigned to GHSA-rhcg-rwhx-qj3j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rhcg-rwhx-qj3j?

GHSA-rhcg-rwhx-qj3j affects the following packages: org.springframework:spring-core (Maven), org.springframework:spring-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-rhcg-rwhx-qj3j?

Update org.springframework:spring-core to 3.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rhcg-rwhx-qj3j is resolved across your whole dependency graph.

How do I detect GHSA-rhcg-rwhx-qj3j in my Maven dependencies?

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.

How do I mitigate GHSA-rhcg-rwhx-qj3j if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-rhcg-rwhx-qj3j?

O3 pinpoints whether GHSA-rhcg-rwhx-qj3j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rhcg-rwhx-qj3j actively exploited in the wild?

No public exploit code has been indexed for GHSA-rhcg-rwhx-qj3j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-rhcg-rwhx-qj3j?

GHSA-rhcg-rwhx-qj3j is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-rhcg-rwhx-qj3j published, and has it been updated?

GHSA-rhcg-rwhx-qj3j was published on May 14, 2022 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-rhcg-rwhx-qj3j

Fix: spring-projects/spring-framework@748167b

GHSA-rhcg-rwhx-qj3j is a Path Traversal vulnerability in org.springframework:spring-core. O3 Security confirms whether GHSA-rhcg-rwhx-qj3j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Limitation of a Pathname to a Restricted Directory in Spring Framework

Also known asCVE-2014-3578

Published

May 14, 2022

Updated

Dec 6, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Dec 6, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

☕org.springframework:spring-core☕org.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

Directory traversal vulnerability in Pivotal Spring Framework 3.x before 3.2.9 and 4.0 before 4.0.5 allows remote attackers to read arbitrary files via a crafted URL.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-core`	≥ 3.0.0&&< 3.2.9	3.2.9
☕Maven	`org.springframework:spring-core`	≥ 4.0.0&&< 4.0.5	4.0.5

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update org.springframework:spring-core to 3.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rhcg-rwhx-qj3j 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-rhcg-rwhx-qj3j 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-rhcg-rwhx-qj3j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Directory traversal vulnerability in Pivotal Spring Framework 3.x before 3.2.9 and 4.0 before 4.0.5 allows remote attackers to read arbitrary files via a crafted URL.

O3 Security · Impact-Aware SCA

Is GHSA-rhcg-rwhx-qj3j in your dependencies?

O3 detects GHSA-rhcg-rwhx-qj3j across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works