# CVE-2009-0217: Apache XML Security For Java vulnerable to authentication bypass by HMAC truncation > Attackers can bypass HMAC-based signature authentication by specifying a small truncation length, affecting multiple XML security implementations. - **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Jul 2009 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2009-0217, DSA-1849-1, GHSA-8hfm-837h-hjg5, RHSA-2009:1428 ## What is CVE-2009-0217? CVE-2009-0217 is a medium-severity vulnerability in Ibm Websphere Application Server, published on 14 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The design of the W3C XML Signature Syntax and Processing (XMLDsig) recommendation, as implemented in products including (1) the Oracle Security Developer Tools component in Oracle Application Server 10.1.2.3, 10.1.3.4, and 10.1.4.3IM; (2) the WebLogic Server component in BEA Product Suite 10.3, 10.0 MP1, 9.2 MP3, 9.1, 9.0, and 8.1 SP6; (3) Mono before 2.4.2.2; (4) XML Security Library before 1.2.12; (5) 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; (6) Sun JDK and JRE Update 14 and earlier; (7) 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. ## Which versions are affected by CVE-2009-0217? 2 open source packages ship an affected version, including org.apache.santuario:xmlsec. It affects 5 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.santuario:xmlsec` | Maven | From 1.4.0 | 1.4.3 | | `org.apache.santuario:xmlsec` | Maven | From 1.4.0 | 1.4.3 | | `xmlsec1` | Red Hat:enterprise_linux:4::as | All versions | 0:1.2.6-3.1 | | `xmlsec1-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.2.6-3.1 | | `xmlsec1-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.2.6-3.1 | | `xmlsec1-openssl` | Red Hat:enterprise_linux:4::as | All versions | 0:1.2.6-3.1 | | `xmlsec1-openssl-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.2.6-3.1 | | `xmlsec1` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.2.6-3.1 | | `xmlsec1-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.2.6-3.1 | | `xmlsec1-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.2.6-3.1 | | `xmlsec1-openssl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.2.6-3.1 | | `xmlsec1-openssl-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.2.6-3.1 | | `xmlsec1` | Red Hat:enterprise_linux:4::es | All versions | 0:1.2.6-3.1 | | `xmlsec1-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.2.6-3.1 | | `xmlsec1-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.2.6-3.1 | | `xmlsec1-openssl` | Red Hat:enterprise_linux:4::es | All versions | 0:1.2.6-3.1 | | `xmlsec1-openssl-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.2.6-3.1 | | `xmlsec1` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.2.6-3.1 | | `xmlsec1-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.2.6-3.1 | | `xmlsec1-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.2.6-3.1 | | `xmlsec1-openssl` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.2.6-3.1 | | `xmlsec1-openssl-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.2.6-3.1 | | `xmlsec1` | Red Hat:enterprise_linux:5::client | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-gnutls` | Red Hat:enterprise_linux:5::client | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-nss` | Red Hat:enterprise_linux:5::client | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-openssl` | Red Hat:enterprise_linux:5::client | All versions | 0:1.2.9-8.1.1 | | `xmlsec1` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-gnutls-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-nss-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-openssl-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.2.9-8.1.1 | | `xmlsec1` | Red Hat:enterprise_linux:5::server | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-gnutls` | Red Hat:enterprise_linux:5::server | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-gnutls-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-nss` | Red Hat:enterprise_linux:5::server | All versions | 0:1.2.9-8.1.1 | | `xmlsec1-nss-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:1.2.9-8.1.1 | Products: Ibm Websphere Application Server, Mono Project Mono, Oracle Application Server, Oracle Bea Product Suite, Oracle Weblogic Server Component. ## How do I fix CVE-2009-0217? Upgrade org.apache.santuario:xmlsec to 1.4.3 or later. ## Is CVE-2009-0217 being exploited? There is no known exploitation of CVE-2009-0217 in the wild and no public exploit code. ## Other vulnerabilities in Ibm Websphere Application Server - [CVE-2015-1920](https://insights.sbomify.com/CVE-2015-1920/): Code injection in n/a (critical 10.0) - [CVE-2013-0462](https://insights.sbomify.com/CVE-2013-0462/): Other in n/a (critical 10.0) - [CVE-2011-1377](https://insights.sbomify.com/CVE-2011-1377/): Security feature bypass in n/a (critical 10.0) - [CVE-2010-3186](https://insights.sbomify.com/CVE-2010-3186/): Other in n/a (critical 10.0) - [CVE-2009-1899](https://insights.sbomify.com/CVE-2009-1899/): Information disclosure in n/a (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2009-0217 and fix it if it is affected. What it is: CVE-2009-0217 is a medium-severity vulnerability in Ibm Websphere Application Server, published on 14 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2009-0217 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.santuario:xmlsec (Maven): affected from 1.4.0; fixed in 1.4.3 - org.apache.santuario:xmlsec (Maven): affected from 1.4.0; fixed in 1.4.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2009-0217/ (Markdown: https://insights.sbomify.com/CVE-2009-0217/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2009-0217 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-0217 - OSV: https://osv.dev/vulnerability/CVE-2009-0217 --- From sbomify Insights: https://insights.sbomify.com/CVE-2009-0217/ Summaries are generated and may contain mistakes; the official description above is the record.