CVE-2013-2461: High severity Oracle JDK vulnerability
It was discovered that the DOMCanonicalizationMethod did not properly verify the canonicalization algorithm. A remote attacker could possibly exploit this flaw to bypass correct XML signature verification.
Other sources
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 21 and earlier and 6 Update 45 and earlier; the Oracle JRockit component in Oracle Fusion Middleware R27.7.5 and earlier and R28.2.7 and earlier; and OpenJDK 7 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Libraries. NOTE: the previous information is from the June and July 2013 CPU. Oracle has not commented on claims from another vendor that this issue allows remote attackers to bypass verification of XML signatures via vectors related to a "Missing check for [a] valid DOMCanonicalizationMethod canonicalization algorithm."
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2013-2461?
The severity of CVE-2013-2461 is classified as high due to its potential impact on XML signature verification.
How do I fix CVE-2013-2461?
To fix CVE-2013-2461, update your Java Runtime Environment or Oracle JDK to the latest version, which contains the necessary security patches.
What versions are affected by CVE-2013-2461?
CVE-2013-2461 affects Oracle JDK versions 1.6.0-update22 through 1.6.0-update43 and certain Oracle JRE 1.7.0 versions.
What is the risk of CVE-2013-2461 for my applications?
The risk of CVE-2013-2461 is that a remote attacker might exploit it to bypass XML signature verification, potentially compromising data integrity.
Is there a workaround for CVE-2013-2461?
There are no officially documented workarounds for CVE-2013-2461, making an update the recommended action.