First published: Mon Jul 13 2015(Updated: )
It was discovered that the DnsClient client class in the JNDI (Java Naming and Directory Interface) component in OpenJDK failed to properly remove information about an outgoing DNS request from the list of outstanding DNS requests when certain errors occurred during DNS resolution. An attacker able to trigger such DNS errors could cause a Java application using JNDI to consume memory and possibly block further DNS resolution (after exhausting all DNS transaction ids).
Credit: secalert_us@oracle.com secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle JRockit | =r28.3.6 | |
Oracle JDK | =1.6.0-update95 | |
Oracle JDK | =1.7.0-update75 | |
Oracle JDK | =1.7.0-update80 | |
Oracle JDK | =1.8.0-update_33 | |
Oracle JDK | =1.8.0-update45 | |
Oracle JRE | =1.6.0-update_95 | |
Oracle JRE | =1.7.0-update_75 | |
Oracle JRE | =1.7.0-update_80 | |
Oracle JRE | =1.8.0-update_33 | |
Oracle JRE | =1.8.0-update_45 | |
debian/openjdk-8 | 8u432-b06-2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this Oracle Java SE vulnerability is CVE-2015-4749.
The severity level of the CVE-2015-4749 vulnerability is medium.
Oracle Java SE 6u95, 7u80, and 8u45 are affected by CVE-2015-4749.
A remote attacker can exploit CVE-2015-4749 through vectors related to JNDI.
You can find more information about CVE-2015-4749 on the Oracle Technology Network and Red Hat Errata websites.