Insufficient Verification of Data Authenticity in Async Http Client
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2013-7398US | medium4.3OT elevated | — | ||
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… | ||||
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/a894583921c11c3b01f160ada36a8bb9d5158e9WEB
- https://github.com/AsyncHttpClient/async-http-client/issues/197WEB
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