CVE-2022-2047 [Low] | Input Validation Bypass in Jetty

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.36%	0.93%	+0.57%
2	2026-06-02	0.57%	0.36%	-0.21%
3	2026-05-22	—	0.57%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.36%

0.93%

+0.57%

2026-06-02

0.57%

0.36%

-0.21%

2026-05-22

—

0.57%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
2.7	3.1	LOW	`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.2	1.4	[email protected]
2.7	3.1	LOW	`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.2	1.4	[email protected]
4.0	2.0	MEDIUM	`AV:N/AC:L/Au:S/C:N/I:P/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:S) A single authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	8.0	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

2.7

3.1

LOW

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.2

1.4

[email protected]

2.7

3.1

LOW

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.2

1.4

[email protected]

4.0

2.0

MEDIUM

AV:N/AC:L/Au:S/C:N/I:P/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:S): A single authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:N): No availability impact.

8.0

2.9

[email protected]

OS Trackers for CVE-2022-2047

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-2047 not yet assigned priority: Debian including 1 source packages (jetty9), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-2047
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2022-2047
`suse`	low	CVE-2022-2047 severity low: SUSE including 97 source package names (jetty-annotations, jetty-annotations-9.4.48-1.1, …), 430 product×package rows across 31 product lines (SUSE Enterprise Storage 7, SUSE Enterprise Storage 7.1, … (31 product lines)): Fixed 256, Known Not Affected 174.	https://www.suse.com/security/cve/CVE-2022-2047/
`ubuntu`	medium	CVE-2022-2047 medium priority: Ubuntu including 3 source packages (jetty, jetty8, jetty9), 42 status rows across 14 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 23, needs-triage 10, not-affected 6, ignored 2, released 1.	https://ubuntu.com/security/CVE-2022-2047

Affected software / configurations for CVE-2022-2047

Vendor	Product	Version	Raw CPE
eclipse	jetty	< 9.4.46	cpe:2.3:a:eclipse:jetty::::::::
eclipse	jetty	>= 10.0.0, < 10.0.9	cpe:2.3:a:eclipse:jetty::::::::
eclipse	jetty	>= 11.0.0, <= 11.0.9	cpe:2.3:a:eclipse:jetty::::::::
debian	debian_linux	10.0	cpe:2.3:o:debian:debian_linux:10.0:::::::*
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*
netapp	element_plug-in_for_vcenter_server	—	cpe:2.3:a:netapp:element_plug-in_for_vcenter_server:-:::::::*
netapp	management_services_for_element_software_and_netapp_hci	—	cpe:2.3:a:netapp:management_services_for_element_software_and_netapp_hci:-:::::::*
netapp	snapcenter	—	cpe:2.3:a:netapp:snapcenter:-:::::::*
netapp	solidfire_\&_hci_storage_node	—	cpe:2.3:a:netapp:solidfire_\&_hci_storage_node:-:::::::*
netapp	hci_compute_node	—	cpe:2.3:h:netapp:hci_compute_node:-:::::::*

References for CVE-2022-2047

URL	Tags
https://github.com/eclipse/jetty.project/security/advisories/GHSA-cj7v-27pg-wf7q	Patch Third Party Advisory
https://lists.debian.org/debian-lts-announce/2022/08/msg00011.html	Mailing List Third Party Advisory
https://security.netapp.com/advisory/ntap-20220901-0006/	Third Party Advisory
https://www.debian.org/security/2022/dsa-5198	Third Party Advisory

URL

CVE-2022-2047

Exploit prediction scoring system (EPSS) score for CVE-2022-2047

Common vulnerability scoring system (CVSS) metrics for CVE-2022-2047

Weakness enumeration for CVE-2022-2047

GitHub Security Advisory for CVE-2022-2047

OS Trackers for CVE-2022-2047

Affected software / configurations for CVE-2022-2047

References for CVE-2022-2047