CVE-2022-2047
LOWCVE-2022-2047 is a low-severity (CVSS 2.7) Improper Input Validation vulnerability in org.eclipse.jetty:jetty-http. O3 Security confirms whether CVE-2022-2047 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Jetty invalid URI parsing may produce invalid HttpURI.authority
Blast Radius
org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-httpReal-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
In Eclipse Jetty versions 9.4.0 thru 9.4.46, and 10.0.0 thru 10.0.9, and 11.0.0 thru 11.0.9 versions, the parsing of the authority segment of an http scheme URI, the Jetty HttpURI class improperly detects an invalid input as a hostname. This can lead to failures in a Proxy scenario.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.jetty:jetty-http | all versions | 9.4.47 |
| ☕Maven | org.eclipse.jetty:jetty-http | ≥ 10.0.0&&< 10.0.10 | 10.0.10 |
| ☕Maven | org.eclipse.jetty:jetty-http | ≥ 11.0.0&&< 11.0.10 | 11.0.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-http. 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.
Fix
Update org.eclipse.jetty:jetty-http to 9.4.47 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2047 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2022-2047 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 CVE-2022-2047. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-2047 in your dependencies?
O3 detects CVE-2022-2047 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.