CVE-2013-7397

Description

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.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
0.993%
chance of exploitation in the next 30 days
higher than 63.2% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2015-06-24Published by the CNA16:00 UTC
  2. 2022-05-13GitHub advisory published (GHSA-8h53-fjgg-g42g)2515 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-8h53-fjgg-g42g, affected packages:

EcosystemPackageVulnerable rangePatched
Mavencom.ning:async-http-client< 1.9.01.9.0

Affected products

VendorProduct
async-http-client_projectasync-http-client
redhatjboss_fuse

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources