Skip to content
Fencer Intel
medium 4.3

CVE-2013-7398 json

Insufficient Verification of Data Authenticity in Async Http Client

published 11y ago modified 4mo ago also GHSA-5c66-6h6g-6q6m , EUVD-2022-2559

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

main/java/com/ning/http/client/AsyncHttpClientConfig.java in Async Http Client (aka AHC or async-http-client) before 1.9.0 does not require a hostname match during verification of X.509 certificates, which allows man-in-the-middle attackers to spoof HTTPS servers via an arbitrary valid certificate.

Patch / fix

  • maven com.ning:async-http-client 1.9.0

Is CVE-2013-7398 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-7398 updated cvss 5.8

async-http-client: missing hostname verification for SSL certificates

  • Red Hat JBoss Data Virtualization 6 async-http-client async-http-client
    affected: no fix available
  • Red Hat JBoss BPMS 6.0
    fixed: vendor fix RHSA-2015:0851
  • Red Hat JBoss BRMS 6.0
    fixed: vendor fix RHSA-2015:0850
  • Red Hat JBoss Fuse 6.2
    fixed: vendor fix RHSA-2015:1176
  • Red Hat JBoss Fuse Service Works 6.0
    fixed: vendor fix RHSA-2015:1551

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven com.ning:async-http-client
<1.9.0
1.9.0

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.