How severe is GHSA-3h6f-g5f3-gc4w?

GHSA-3h6f-g5f3-gc4w has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3h6f-g5f3-gc4w?

GHSA-3h6f-g5f3-gc4w affects the following packages: org.springframework.security:spring-security-config (Maven), org.springframework.security:spring-security-config (Maven), org.springframework.security:spring-security-config (Maven), org.springframework.security:spring-security-config (Maven), org.springframework.security:spring-security-config (Maven). Ecosystems affected: Maven.

How do I fix GHSA-3h6f-g5f3-gc4w?

Update org.springframework.security:spring-security-config to 5.6.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3h6f-g5f3-gc4w is resolved across your whole dependency graph.

How do I detect GHSA-3h6f-g5f3-gc4w in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-config. 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-3h6f-g5f3-gc4w 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-3h6f-g5f3-gc4w?

O3 pinpoints whether GHSA-3h6f-g5f3-gc4w 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-3h6f-g5f3-gc4w actively exploited in the wild?

No public exploit code has been indexed for GHSA-3h6f-g5f3-gc4w 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 is the EPSS score for GHSA-3h6f-g5f3-gc4w?

GHSA-3h6f-g5f3-gc4w has an EPSS (Exploit Prediction Scoring System) score of 3.5%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-3h6f-g5f3-gc4w published, and has it been updated?

GHSA-3h6f-g5f3-gc4w was published on July 19, 2023 and was last updated on October 28, 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

GHSA-3h6f-g5f3-gc4w

CRITICAL

Access Control Bypass in Spring Security

Also known asCVE-2023-34034

Published

Jul 19, 2023

Updated

Oct 28, 2024

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

3.5%probability of exploitation in next 30 days

Lower Risk88th percentile-45.82%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected

☕org.springframework.security:spring-security-config☕org.springframework.security:spring-security-config☕org.springframework.security:spring-security-config☕org.springframework.security:spring-security-config☕org.springframework.security:spring-security-config

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

Using "**" as a pattern in Spring Security configuration for WebFlux creates a mismatch in pattern matching between Spring Security and Spring WebFlux, and the potential for a security bypass.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.security:spring-security-config`	≥ 5.6.0&&< 5.6.12	5.6.12
☕Maven	`org.springframework.security:spring-security-config`	≥ 5.7.0&&< 5.7.10	5.7.10
☕Maven	`org.springframework.security:spring-security-config`	≥ 5.8.0&&< 5.8.5	5.8.5
☕Maven	`org.springframework.security:spring-security-config`	≥ 6.0.0&&< 6.0.5	6.0.5
☕Maven	`org.springframework.security:spring-security-config`	≥ 6.1.0&&< 6.1.2	6.1.2

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.security:spring-security-config. 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.security:spring-security-config to 5.6.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3h6f-g5f3-gc4w 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-3h6f-g5f3-gc4w 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-3h6f-g5f3-gc4w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Using "**" as a pattern in Spring Security configuration for WebFlux creates a mismatch in pattern matching between Spring Security and Spring WebFlux, and the potential for a security bypass.

O3 Security · Impact-Aware SCA

Is GHSA-3h6f-g5f3-gc4w in your dependencies?

O3 detects GHSA-3h6f-g5f3-gc4w 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