CVE-2013-7397

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

1.0% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2015-06-24 16:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:01 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.0% in the next 30 days (EPSS).
• Severity: 4.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2015-06-24 16:59 UTC

Last modified

2026-06-17 00:01 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-345

Record status

Modified

Affected

• Redhat Jboss Fuse ≤ 6.1.0
• async-http-client Project async-http-client ≤ 1.9.0

Attack profile CVSS 2.0 · 4.3

Attack vector

Network

Complexity

Medium

Authentication

None

Confidentiality

None

Integrity

Partial

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2013-7397.md and follow it. Check whether this project is affected by CVE-2013-7397. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge