CVE-2017-14063 Improper Input Validation in async-http-client
Attackers can trick the Async Http Client into connecting to an unintended host via fragment identifiers, bypassing SSRF protections.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2017-14063?
CVE-2017-14063 is a high-severity server-side request forgery vulnerability in n/a, published on 31 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-20
Which versions are affected by CVE-2017-14063?
2 open source packages ship an affected version, including org.asynchttpclient:async-http-client. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.asynchttpclient:async-http-client Maven | All versions | 2.0.35 |
org.asynchttpclient:async-http-client Maven | All versions | 2.0.35 |
Products include Asynchttpclient Project Async-Http-Client.
How do I fix CVE-2017-14063?
Upgrade org.asynchttpclient:async-http-client to 2.0.35 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2017-14063 being exploited?
There is no known exploitation of CVE-2017-14063 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-93jq-624g-4p9p.