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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
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 |
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.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-06T18:09:16.606Z
Reserved: 2014-08-25T00:00:00
Link: CVE-2013-7397
No data.
Status : Deferred
Published: 2015-06-24T16:59:00.093
Modified: 2025-04-12T10:46:40.837
Link: CVE-2013-7397
OpenCVE Enrichment
No data.
EUVD
Github GHSA