First published: Tue Aug 26 2014(Updated: )
Async Http Client (aka AHC or async-http-client) before 1.9.0 skips X.509 certificate verification unless both a keyStore location and a trustStore location are explicitly set, which allows man-in-the-middle attackers to spoof HTTPS servers by presenting an arbitrary certificate during use of a typical AHC configuration, as demonstrated by a configuration that does not send client certificates.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/async-http-client | <1.9.0 | 1.9.0 |
maven/com.ning:async-http-client | <1.9.0 | 1.9.0 |
Red Hat JBoss Fuse | <=6.1.0 | |
Jenkins SCM HTTP Client | <=1.9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-7397 is classified as a High severity vulnerability due to its potential for man-in-the-middle attacks.
To fix CVE-2013-7397, upgrade Async Http Client to version 1.9.0 or later.
Versions of Async Http Client earlier than 1.9.0 are affected by CVE-2013-7397.
Yes, CVE-2013-7397 affects software packages including Async Http Client, Red Hat JBoss Fuse, and others before version 1.9.0.
Yes, CVE-2013-7397 can be exploited in production environments if the vulnerable software is used without proper certificate verification.