OESA-2023-1031 (CVE-2022-2048)
Vulnerability from osv_openeuler – Published: 2023-01-13 11:05 – Updated: 2026-08-06 11:05 – Source websiteJetty is a 100% Java HTTP Server and Servlet Container. This means that you do not need to configure and run a separate web server (like Apache) in order to use Java, servlets and JSPs to generate dynamic content. Jetty is a fully featured web server for static and dynamic content. Unlike separate server/container solutions, this means that your web server and web application run in the same process, without interconnection overheads and complications. Furthermore, as a pure java component, Jetty can be simply included in your application for demonstration, distribution or deployment.Jetty is available on all Java supported platforms.
Security Fix(es):
In Eclipse Jetty HTTP/2 server implementation, when encountering an invalid HTTP/2 request, the error handling has a bug that can wind up not properly cleaning up the active connections and associated resources. This can lead to a Denial of Service scenario where there are no enough resources left to process good requests.(CVE-2022-2048)
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.(CVE-2022-2047)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"noarch": [
"jetty-proxy-9.4.16-3.oe1.noarch.rpm",
"jetty-xml-9.4.16-3.oe1.noarch.rpm",
"jetty-httpservice-9.4.16-3.oe1.noarch.rpm",
"jetty-osgi-boot-9.4.16-3.oe1.noarch.rpm",
"jetty-client-9.4.16-3.oe1.noarch.rpm",
"jetty-spring-9.4.16-3.oe1.noarch.rpm",
"jetty-maven-plugin-9.4.16-3.oe1.noarch.rpm",
"jetty-project-9.4.16-3.oe1.noarch.rpm",
"jetty-javadoc-9.4.16-3.oe1.noarch.rpm",
"jetty-continuation-9.4.16-3.oe1.noarch.rpm",
"jetty-nosql-9.4.16-3.oe1.noarch.rpm",
"jetty-http2-http-client-transport-9.4.16-3.oe1.noarch.rpm",
"jetty-javax-websocket-server-impl-9.4.16-3.oe1.noarch.rpm",
"jetty-plus-9.4.16-3.oe1.noarch.rpm",
"jetty-osgi-boot-warurl-9.4.16-3.oe1.noarch.rpm",
"jetty-websocket-server-9.4.16-3.oe1.noarch.rpm",
"jetty-io-9.4.16-3.oe1.noarch.rpm",
"jetty-9.4.16-3.oe1.noarch.rpm",
"jetty-server-9.4.16-3.oe1.noarch.rpm",
"jetty-unixsocket-9.4.16-3.oe1.noarch.rpm",
"jetty-websocket-api-9.4.16-3.oe1.noarch.rpm",
"jetty-jaspi-9.4.16-3.oe1.noarch.rpm",
"jetty-websocket-common-9.4.16-3.oe1.noarch.rpm",
"jetty-servlet-9.4.16-3.oe1.noarch.rpm",
"jetty-annotations-9.4.16-3.oe1.noarch.rpm",
"jetty-deploy-9.4.16-3.oe1.noarch.rpm",
"jetty-http2-server-9.4.16-3.oe1.noarch.rpm",
"jetty-webapp-9.4.16-3.oe1.noarch.rpm",
"jetty-fcgi-server-9.4.16-3.oe1.noarch.rpm",
"jetty-osgi-alpn-9.4.16-3.oe1.noarch.rpm",
"jetty-jndi-9.4.16-3.oe1.noarch.rpm",
"jetty-security-9.4.16-3.oe1.noarch.rpm",
"jetty-http-9.4.16-3.oe1.noarch.rpm",
"jetty-infinispan-9.4.16-3.oe1.noarch.rpm",
"jetty-jstl-9.4.16-3.oe1.noarch.rpm",
"jetty-util-ajax-9.4.16-3.oe1.noarch.rpm",
"jetty-cdi-9.4.16-3.oe1.noarch.rpm",
"jetty-servlets-9.4.16-3.oe1.noarch.rpm",
"jetty-ant-9.4.16-3.oe1.noarch.rpm",
"jetty-http2-common-9.4.16-3.oe1.noarch.rpm",
"jetty-quickstart-9.4.16-3.oe1.noarch.rpm",
"jetty-jsp-9.4.16-3.oe1.noarch.rpm",
"jetty-alpn-client-9.4.16-3.oe1.noarch.rpm",
"jetty-rewrite-9.4.16-3.oe1.noarch.rpm",
"jetty-http-spi-9.4.16-3.oe1.noarch.rpm",
"jetty-jspc-maven-plugin-9.4.16-3.oe1.noarch.rpm",
"jetty-start-9.4.16-3.oe1.noarch.rpm",
"jetty-http2-hpack-9.4.16-3.oe1.noarch.rpm",
"jetty-websocket-client-9.4.16-3.oe1.noarch.rpm",
"jetty-jmx-9.4.16-3.oe1.noarch.rpm",
"jetty-fcgi-client-9.4.16-3.oe1.noarch.rpm",
"jetty-http2-client-9.4.16-3.oe1.noarch.rpm",
"jetty-osgi-boot-jsp-9.4.16-3.oe1.noarch.rpm",
"jetty-websocket-servlet-9.4.16-3.oe1.noarch.rpm",
"jetty-util-9.4.16-3.oe1.noarch.rpm",
"jetty-javax-websocket-client-impl-9.4.16-3.oe1.noarch.rpm",
"jetty-jaas-9.4.16-3.oe1.noarch.rpm",
"jetty-alpn-server-9.4.16-3.oe1.noarch.rpm"
],
"src": [
"jetty-9.4.16-3.oe1.src.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP3",
"name": "jetty",
"purl": "pkg:rpm/openEuler/jetty\u0026distro=openEuler-20.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "9.4.16-3.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "Jetty is a 100% Java HTTP Server and Servlet Container. This means that you do not need to configure and run a separate web server (like Apache) in order to use Java, servlets and JSPs to generate dynamic content. Jetty is a fully featured web server for static and dynamic content. Unlike separate server/container solutions, this means that your web server and web application run in the same process, without interconnection overheads and complications. Furthermore, as a pure java component, Jetty can be simply included in your application for demonstration, distribution or deployment.Jetty is available on all Java supported platforms.\r\n\r\nSecurity Fix(es):\r\n\r\nIn Eclipse Jetty HTTP/2 server implementation, when encountering an invalid HTTP/2 request, the error handling has a bug that can wind up not properly cleaning up the active connections and associated resources. This can lead to a Denial of Service scenario where there are no enough resources left to process good requests.(CVE-2022-2048)\r\n\r\nIn 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.(CVE-2022-2047)",
"id": "OESA-2023-1031",
"modified": "2026-08-06T11:05:30Z",
"published": "2023-01-13T11:05:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1031"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-2048"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-2047"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "jetty security update",
"upstream": [
"CVE-2022-2048",
"CVE-2022-2047"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.