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.
CVE-2013-7397
MEDIUMCVSS v2 · 4.34.3—
EchelonGraph scoreLOW confidence
This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:N/I:P/A:N. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 1.0% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.
Sources: epss, nvd_v2
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS v2: 4.3Exploit: None knownExposed services: —
A fix is available — apply it.
Internet exposure
The internet-exposure footprint is temporarily unavailable — the KEV-Exposure radar's record for this CVE could not be loaded just now. That is not a finding of zero exposed services; please retry shortly.
- CVSS v2.0 (legacy)
- 4.3MEDIUMNVD never assigned a CVSS v3 rating to this CVE
- EG Score
- 4.3MEDIUMlow confidence
- EG Risk
- 24EG Risk 24/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation1% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.0%
- EPSS %ILE
- 61st
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
June 24, 2015
Last Modified
May 6, 2026
Advisory Details (1)
0
NONE
2015-06-24 16:59:00.093+00
Affected: [{"url": "http://openwall.com/lists/oss-security/2014/08/26/1", "source": "[email protected]"}, {"url": "http://rhn.redhat.com/errata/RHSA-2015-0850.html", "source": "[email protected]"}, {"url": "http://rhn.redhat.com/errata/RHSA-2015-0851.html", "source": "[email protected]"}, {"url": "http://rhn.redhat.com/errata/RHSA-2015-1176.html", "source": "[email protected]"}, {"url": "http://rhn.redhat.com/errata/RHSA-2015-1551.html", "source": "[email protected]"}, {"url": "http://www.securityfocus.com/bid/69316", "source": "[email protected]"}, {"url": "https://github.com/AsyncHttpClient/async-http-client/issues/352", "tags": ["Vendor Advisory"], "source": "[email protected]"}, {"url": "https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8%40%3Ccommits.pulsar.apache.org%3E", "source": "[email protected]"}, {"url": "https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26%40%3Ccommits.pulsar.apache.org%3E", "source": "[email protected]"}, {"url": "https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-06-20", "source": "[email protected]"}, {"url": "http://openwall.com/lists/oss-security/2014/08/26/1", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://rhn.redhat.com/errata/RHSA-2015-0850.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://rhn.redhat.com/errata/RHSA-2015-0851.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://rhn.redhat.com/errata/RHSA-2015-1176.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://rhn.redhat.com/errata/RHSA-2015-1551.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.securityfocus.com/bid/69316", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/AsyncHttpClient/async-http-client/issues/352", "tags": ["Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8%40%3Ccommits.pulsar.apache.org%3E", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26%40%3Ccommits.pulsar.apache.org%3E", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-06-20", "source": "af854a3a-2127-422b-91ae-364da2661108"}]
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.Vendor Advisories for CVE-2013-7397(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2015:1176Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Fuse 6.2.0 update
- RHSA-2015:0850Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss BRMS 6.1.0 update
- RHSA-2015:0851Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss BPM Suite 6.1.0 update
Patch Availability(5)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | async-http-client | 2015-08-05 | redhat |
| redhat | patch | 2015-06-23 | redhat |
| Debian:11 | async-http-client @ 1.6.5-3 (the fix for one version range) | — | 0 |
| Debian:12 | async-http-client @ 1.6.5-3 (the fix for one version range) | — | 0 |
| Maven | com.ning:async-http-client @ 1.9.0 (fixes 1.0.0 ... 1.9.0-BETA9 (86 versions)) | — | 0 |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Related CVEs
Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.
Frequently asked(4)
What is CVE-2013-7397?
CVE-2013-7397 is a medium vulnerability published on June 24, 2015. 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…
When was CVE-2013-7397 disclosed?
CVE-2013-7397 was first published on June 24, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-7397 actively exploited?
CVE-2013-7397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
How do I remediate CVE-2013-7397?
A fix for CVE-2013-7397 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2013-7397 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2013-7397
Is Your Infrastructure Affected by CVE-2013-7397?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.