CVE-2017-14063

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.

Severity
HIGH
CVSS v3
7.5
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N · source nvd
Exploit chance (EPSS)
3.046%
chance of exploitation in the next 30 days
higher than 87.8% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2017-08-31Published by the CNA16:00 UTC
  2. 2018-10-19GitHub advisory published (GHSA-93jq-624g-4p9p)414 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-93jq-624g-4p9p, affected packages:

PackageVulnerable versionsFixed in
Maven org.asynchttpclient:async-http-clientbefore 2.0.352.0.35

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
asynchttpclient_project async-http-clientbefore 2.0.35fixed in 2.0.352.0.35

Products and versions as NVD and the vendor that published the CVE list them.

References

28 references in total; the first 20 are shown.

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources