How severe is CVE-2013-7397?

No CVSS score has been assigned to CVE-2013-7397 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-7397?

CVE-2013-7397 affects the following packages: com.ning:async-http-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-7397?

Update com.ning:async-http-client to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7397 is resolved across your whole dependency graph.

How do I detect CVE-2013-7397 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.ning:async-http-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-7397 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2013-7397 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-7397 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-7397?

CVE-2013-7397 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-7397?

CVE-2013-7397 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-7397 published, and has it been updated?

CVE-2013-7397 was published on June 24, 2015 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-7397 — async-http-client

Fix: AsyncHttpClient/async-http-client@dfacb8e

CVE-2013-7397 is a CWE-345 vulnerability in com.ning:async-http-client. A fix is available for com.ning:async-http-client — see the affected versions and patch details below.

Insufficient Verification of Data Authenticity in Async Http Client

Also known asGHSA-8h53-fjgg-g42g

Published

Jun 24, 2015

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕com.ning:async-http-client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.ning:async-http-client`	all versions	1.9.0`com.ning:async-http-client:1.9.0`

Affected Products

2 products · 2 configurations

Application

async-http-clientasync-http-client_project

≤ 1.9.0

range

Application

jboss fuseredhat

≤ 6.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.ning:async-http-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.ning:async-http-client to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7397 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat JBoss BPMS 6.0	`async-http-client`	RHSA-2015:0851
Red Hat JBoss BRMS 6.0	`async-http-client`	RHSA-2015:0850
Red Hat JBoss Fuse 6.2	see advisory	RHSA-2015:1176
Red Hat JBoss Fuse Service Works 6.0	`async-http-client`	RHSA-2015:1551

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-7397 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works