async-http-client: SSL/TLS certificate verification is disabled under certain conditions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat JBoss BPMS 6.0 | |||
| async-http-client | cpe:/a:redhat:jboss_bpms:6.0 | RHSA-2015:0851 | 2015-04-16T00:00:00Z |
| Red Hat JBoss BRMS 6.0 | |||
| async-http-client | cpe:/a:redhat:jboss_brms:6.0 | RHSA-2015:0850 | 2015-04-16T00:00:00Z |
| Red Hat JBoss Fuse 6.2 | |||
| cpe:/a:redhat:jboss_fuse:6.2.0 | RHSA-2015:1176 | 2015-06-23T00:00:00Z | |
| Red Hat JBoss Fuse Service Works 6.0 | |||
| async-http-client | cpe:/a:redhat:jboss_fuse_service_works:6.0 | RHSA-2015:1551 | 2015-08-05T00:00:00Z |
No data available yet.
| 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 |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.993% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.