First published: Tue Jan 17 2017(Updated: )
It was discovered that the LdapLoginModule class in the Java Authentication and Authorization Service (JAAS) component of OpenJDK did not use a correct way to extract user DN from a result of the LDAP query used to locate user in an LDAP database. A specially crafted user LDAP entry could cause the application to use incorrect DN.
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle JDK 6 | =1.6-update_131 | |
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.6-update_131 | |
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 | |
debian/openjdk-8 | 8u442-ga-2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-3252 is rated as a high severity vulnerability due to its potential impact on user authentication.
To fix CVE-2017-3252, update your Java environment to the latest version as provided by Oracle.
CVE-2017-3252 affects specific versions of Oracle JDK and JRE including 1.6-update_131, 1.7-update_121, and 1.8-update_111 and 1.8-update_112.
CVE-2017-3252 can be exploited through specially crafted LDAP entries that allow unauthorized access during authentication.
Yes, CVE-2017-3252 is remotely exploitable if the LDAP authentication is utilized in the affected environments.