Approved changes feed: RSS · Atom

cpe:2.3:a:async-http-client_project:async-http-client:*:beta24:*:*:*:*:*:*

part: a version: * update: beta24

VendorAsync Http Client Project (a5b5513a-b406-5a5f-91be-60e38d80e2bb)
ProductAsync Http Client (dfbb7a2d-e61d-5a08-a971-aa41b9880b6b)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/asynchttpclient/async-http-client purl2cpe 2026-06-01 10:12:38.441943
pkg:golang/github.com/asynchttpclient/async-http-client purl2cpe 2026-06-01 10:12:38.441946
pkg:maven/org.asynchttpclient/async-http-client purl2cpe 2026-06-01 10:12:38.441949

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2013-7398 vulnerable 2026-06-08 05:05:10.238968 Details available
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.
Published: 2015-06-24T16:00:00.000Z
Updated: 2024-08-06T18:09:16.513Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2013-7397 vulnerable 2026-06-08 05:05:10.238446 Details available
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.
Published: 2015-06-24T16:00:00.000Z
Updated: 2024-08-06T18:09:16.606Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.