First published: Sun Nov 04 2012(Updated: )
Amazon Elastic Load Balancing API Tools does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate, related to overriding the default JDK X509TrustManager.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Amazon Elastic Load Balancing | ||
Amazon Elastic Load Balancing | =1.0 | |
Amazon Elastic Load Balancing | =1.0-1 | |
Amazon Elastic Load Balancing | =1.0.3.4 | |
Amazon Elastic Load Balancing | =1.0.9.3 | |
Amazon Elastic Load Balancing | =1.0.10.0 | |
Amazon Elastic Load Balancing | =1.0.11.1 | |
Amazon Elastic Load Balancing | =1.0.12.0 | |
Amazon Elastic Load Balancing | =1.0.14.3 | |
Amazon Elastic Load Balancing | =1.0.15.1 | |
Amazon Elastic Load Balancing | =1.0.17.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-5781 is classified as medium severity due to its potential to allow man-in-the-middle attacks.
To fix CVE-2012-5781, ensure that server hostname verification is implemented in your SSL/TLS connections.
CVE-2012-5781 affects various versions of Amazon Elastic Load Balancing.
Yes, CVE-2012-5781 can be exploited remotely by attackers with access to intercept the SSL connection.
CVE-2012-5781 can lead to unauthorized access and data exposure due to fraudulent SSL certificate acceptance.