async-http-client: Invalid URL parsing with '?'
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 |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat JBoss Fuse 7 | |||
| async-http-client | cpe:/a:redhat:jboss_fuse:7 | RHSA-2018:2669 | 2018-09-11T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-0557 | Async Http Client (aka async-http-client) before 2.0.35 can be tricked into connecting to a host different from the one extracted by java.net.URI if a '?' character occurs in a fragment identifier. Similar bugs were previously identified in cURL (CVE-2016-8624) and Oracle Java 8 java.net.URL. |
Github GHSA |
GHSA-93jq-624g-4p9p | Improper Input Validation in async-http-client |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 3.0% (3.046% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.