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.
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jboss_fuse | Redhat | * | 6.1.0 (including) |
| Red Hat JBoss BPMS 6.0 | RedHat | async-http-client | * |
| Red Hat JBoss BRMS 6.0 | RedHat | async-http-client | * |
| Red Hat JBoss Fuse 6.2 | RedHat | * | |
| Red Hat JBoss Fuse Service Works 6.0 | RedHat | async-http-client | * |
| Async-http-client | Ubuntu | precise | * |
| Async-http-client | Ubuntu | trusty | * |
| Async-http-client | Ubuntu | trusty/esm | * |
| Async-http-client | Ubuntu | upstream | * |
| Async-http-client | Ubuntu | utopic | * |
| Async-http-client | Ubuntu | vivid | * |
| Async-http-client | Ubuntu | wily | * |