Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-93jq-624g-4p9p

HIGH

GHSA-93jq-624g-4p9p is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in org.asynchttpclient:async-http-client. O3 Security confirms whether GHSA-93jq-624g-4p9p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Input Validation in async-http-client

Also known asCVE-2017-14063
Published
Oct 19, 2018
Updated
Mar 14, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
org.asynchttpclient:async-http-client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.asynchttpclient:async-http-clientall versions2.0.35

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.asynchttpclient:async-http-client. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.asynchttpclient:async-http-client to 2.0.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-93jq-624g-4p9p is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-93jq-624g-4p9p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-93jq-624g-4p9p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-93jq-624g-4p9p in your dependencies?

O3 detects GHSA-93jq-624g-4p9p across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.