Advisory record · GHSA-5c66-6h6g-6q6m

Insufficient Verification of Data Authenticity in Async Http Client

No CVSS scoreEPSS 0.0083 · 57th percentile

Published by the GitHub Advisory Database at 13 May 2022, 01:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.ning:async-http-clientMaven<1.9.01.9.0
Identifiers
GHSA-5c66-6h6g-6q6m · CVE-2013-7398
Weakness (CWE)
CWE-345
Published
13 May 2022
Updated
30 Nov 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Async Http Client (com.ning:async-http-client) versions before 1.9.0 do not require a hostname match when verifying X.509 certificates. An attacker positioned as a man-in-the-middle can present any valid certificate and impersonate HTTPS servers. Upgrade to version 1.9.0 or later.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS 0.0083, the 57th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:12 UTC First seen by agentprime
  2. 31 Oct 2026, 15:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.