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.
Advisories
Source ID Title
EUVD EUVD EUVD-2022-3182 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.
Github GHSA Github GHSA GHSA-8h53-fjgg-g42g Insufficient Verification of Data Authenticity in Async Http Client
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-06T18:09:16.606Z

Reserved: 2014-08-25T00:00:00

Link: CVE-2013-7397

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2015-06-24T16:59:00.093

Modified: 2025-04-12T10:46:40.837

Link: CVE-2013-7397

cve-icon Redhat

Severity : Important

Publid Date: 2013-07-30T00:00:00Z

Links: CVE-2013-7397 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses