Insufficient Verification of Data Authenticity in Async Http Client
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2013-7397US | medium4.3OT elevated | — | ||
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, whi… | ||||
02
references
External citations — patches, advisories, analysis.
- http://openwall.com/lists/oss-security/2014/08/26/1WEB
- http://rhn.redhat.com/errata/RHSA-2015-0850.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2015-0851.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2015-1176.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2015-1551.htmlWEB
- https://github.com/AsyncHttpClient/async-http-clientPACKAGE
- https://github.com/AsyncHttpClient/async-http-client/commit/dfacb8e05d0822c7b2024c452554bd8e1d6221d8WEB
- https://github.com/AsyncHttpClient/async-http-client/issues/352WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan