How severe is GHSA-8hfm-837h-hjg5?

No CVSS score has been assigned to GHSA-8hfm-837h-hjg5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8hfm-837h-hjg5?

GHSA-8hfm-837h-hjg5 affects the following packages: org.apache.santuario:xmlsec (Maven). Ecosystems affected: Maven.

How do I fix GHSA-8hfm-837h-hjg5?

Update org.apache.santuario:xmlsec to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8hfm-837h-hjg5 is resolved across your whole dependency graph.

How do I detect GHSA-8hfm-837h-hjg5 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.santuario:xmlsec. 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-8hfm-837h-hjg5 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-8hfm-837h-hjg5?

O3 pinpoints whether GHSA-8hfm-837h-hjg5 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-8hfm-837h-hjg5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8hfm-837h-hjg5 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-8hfm-837h-hjg5?

GHSA-8hfm-837h-hjg5 has an EPSS (Exploit Prediction Scoring System) score of 6.3%, placing it in the 93th 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-8hfm-837h-hjg5 published, and has it been updated?

GHSA-8hfm-837h-hjg5 was published on May 2, 2022 and was last updated on December 7, 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-8hfm-837h-hjg5

Apache XML Security For Java vulnerable to authentication bypass by HMAC truncation

Also known asCVE-2009-0217

Published

May 2, 2022

Updated

Dec 7, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

6.3%probability of exploitation in next 30 days

Lower Risk93th percentile+4.13%

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

1 pkg affected

☕org.apache.santuario:xmlsec

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

The design of the W3C XML Signature Syntax and Processing (XMLDsig) recommendation, as implemented in multiple products.

The Apache XML Security (Java) is affected by the vulnerability published in US-Cert VU #466161. See: http://www.kb.cert.org/vuls/id/466161 for more information. This bug can allow an attacker to bypass authentication by inserting/modifying a small HMAC truncation length parameter in the XML Signature HMAC based SignatureMethod algorithms.

An inexhaustive list of additional affected products includes:

the Oracle Security Developer Tools component in Oracle Application Server 10.1.2.3, 10.1.3.4, and 10.1.4.3IM;
the WebLogic Server component in BEA Product Suite 10.3, 10.0 MP1, 9.2 MP3, 9.1, 9.0, and 8.1 SP6;
Mono before 2.4.2.2;
XML Security Library before 1.2.12;
IBM WebSphere Application Server Versions 6.0 through 6.0.2.33, 6.1 through 6.1.0.23, and 7.0 through 7.0.0.1;
Sun JDK and JRE Update 14 and earlier;
Microsoft .NET Framework 3.0 through 3.0 SP2, 3.5, and 4.0; and other products uses a parameter that defines an HMAC truncation length (HMACOutputLength) but does not require a minimum for this length, which allows attackers to spoof HMAC-based signatures and bypass authentication by specifying a truncation length with a small number of bits.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.santuario:xmlsec`	≥ 1.4.0&&< 1.4.3	1.4.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.santuario:xmlsec. 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.apache.santuario:xmlsec to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8hfm-837h-hjg5 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-8hfm-837h-hjg5 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-8hfm-837h-hjg5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The design of the W3C XML Signature Syntax and Processing (XMLDsig) recommendation, as implemented in multiple products. The Apache XML Security (Java) is affected by the vulnerability published in US-Cert VU #466161. See: http://www.kb.cert.org/vuls/id/466161 for more information. This bug can allow an attacker to bypass authentication by inserting/modifying a small HMAC truncation length parameter in the XML Signature HMAC based SignatureMethod algorithms. An inexhaustive list of additional affected products includes: 1. the Oracle Security Developer Tools component in Oracle Application

O3 Security · Impact-Aware SCA

Is GHSA-8hfm-837h-hjg5 in your dependencies?

O3 detects GHSA-8hfm-837h-hjg5 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