First published: Mon Jan 16 2017(Updated: )
It was discovered that the ObjectIdentifier class in the Libraries component of OpenJDK did not check the length of the object identifier read from the input before allocating memory to store the OID. An attacker able to make a Java application to decode a specially crafted DER input could cause the application to use an excessive amount of memory. The DER encoding is used in e.g. X.509 certificates or LDAP protocol.
Credit: secalert_us@oracle.com secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/openjdk-8 | 8u432-b06-2 | |
Oracle JDK 6 | =1.7-update_121 | |
Oracle JDK 6 | =1.8-update_111 | |
Oracle JDK 6 | =1.8-update_112 | |
Oracle Java Runtime Environment (JRE) | =1.7-update_121 | |
Oracle Java Runtime Environment (JRE) | =1.8-update_111 | |
Oracle Java Runtime Environment (JRE) | =1.8-update_112 | |
BEA JRockit | =r28.3.12 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-5547 is classified as a high severity vulnerability due to its potential for code execution upon decoding malicious input.
To fix CVE-2016-5547, update your OpenJDK to a version that includes the security patch for this vulnerability.
CVE-2016-5547 affects multiple versions including specific updates of Oracle JDK, JRE, and OpenJDK.
Yes, CVE-2016-5547 can potentially be exploited remotely if an attacker sends specially crafted DER input to a vulnerable Java application.
The potential impacts of CVE-2016-5547 include denial of service or possibly arbitrary code execution in affected applications.