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.
Metrics
Affected Vendors & Products
Advisories
| 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 |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-05T19:13:41.830Z
Reserved: 2017-08-31T00:00:00
Link: CVE-2017-14063
No data.
Status : Deferred
Published: 2017-08-31T16:29:00.303
Modified: 2025-04-20T01:37:25.860
Link: CVE-2017-14063
OpenCVE Enrichment
No data.
EUVD
Github GHSA