OESA-2021-1166 (CVE-2020-27223)

Vulnerability from osv_openeuler – Published: 2021-05-06 11:04 – Updated: 2026-08-06 11:04 – Source website
VLAI
Summary
jetty security update
Details

%global desc \ 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. %{desc} %global extdesc %{desc}\ \ This package contains

Security Fix(es):

In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality” (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values.(CVE-2020-27223)

In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.(CVE-2021-28165)

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "noarch": [
          "jetty-http-spi-9.4.15-7.oe1.noarch.rpm",
          "jetty-websocket-servlet-9.4.15-7.oe1.noarch.rpm",
          "jetty-jaas-9.4.15-7.oe1.noarch.rpm",
          "jetty-javadoc-9.4.15-7.oe1.noarch.rpm",
          "jetty-javax-websocket-client-impl-9.4.15-7.oe1.noarch.rpm",
          "jetty-xml-9.4.15-7.oe1.noarch.rpm",
          "jetty-io-9.4.15-7.oe1.noarch.rpm",
          "jetty-maven-plugin-9.4.15-7.oe1.noarch.rpm",
          "jetty-osgi-boot-9.4.15-7.oe1.noarch.rpm",
          "jetty-osgi-boot-jsp-9.4.15-7.oe1.noarch.rpm",
          "jetty-continuation-9.4.15-7.oe1.noarch.rpm",
          "jetty-infinispan-9.4.15-7.oe1.noarch.rpm",
          "jetty-fcgi-server-9.4.15-7.oe1.noarch.rpm",
          "jetty-http2-http-client-transport-9.4.15-7.oe1.noarch.rpm",
          "jetty-osgi-alpn-9.4.15-7.oe1.noarch.rpm",
          "jetty-spring-9.4.15-7.oe1.noarch.rpm",
          "jetty-ant-9.4.15-7.oe1.noarch.rpm",
          "jetty-nosql-9.4.15-7.oe1.noarch.rpm",
          "jetty-project-9.4.15-7.oe1.noarch.rpm",
          "jetty-http2-client-9.4.15-7.oe1.noarch.rpm",
          "jetty-jndi-9.4.15-7.oe1.noarch.rpm",
          "jetty-servlets-9.4.15-7.oe1.noarch.rpm",
          "jetty-javax-websocket-server-impl-9.4.15-7.oe1.noarch.rpm",
          "jetty-servlet-9.4.15-7.oe1.noarch.rpm",
          "jetty-util-9.4.15-7.oe1.noarch.rpm",
          "jetty-deploy-9.4.15-7.oe1.noarch.rpm",
          "jetty-httpservice-9.4.15-7.oe1.noarch.rpm",
          "jetty-plus-9.4.15-7.oe1.noarch.rpm",
          "jetty-rewrite-9.4.15-7.oe1.noarch.rpm",
          "jetty-websocket-api-9.4.15-7.oe1.noarch.rpm",
          "jetty-websocket-client-9.4.15-7.oe1.noarch.rpm",
          "jetty-fcgi-client-9.4.15-7.oe1.noarch.rpm",
          "jetty-http-9.4.15-7.oe1.noarch.rpm",
          "jetty-jstl-9.4.15-7.oe1.noarch.rpm",
          "jetty-osgi-boot-warurl-9.4.15-7.oe1.noarch.rpm",
          "jetty-websocket-common-9.4.15-7.oe1.noarch.rpm",
          "jetty-webapp-9.4.15-7.oe1.noarch.rpm",
          "jetty-http2-common-9.4.15-7.oe1.noarch.rpm",
          "jetty-util-ajax-9.4.15-7.oe1.noarch.rpm",
          "jetty-proxy-9.4.15-7.oe1.noarch.rpm",
          "jetty-cdi-9.4.15-7.oe1.noarch.rpm",
          "jetty-jmx-9.4.15-7.oe1.noarch.rpm",
          "jetty-server-9.4.15-7.oe1.noarch.rpm",
          "jetty-unixsocket-9.4.15-7.oe1.noarch.rpm",
          "jetty-start-9.4.15-7.oe1.noarch.rpm",
          "jetty-websocket-server-9.4.15-7.oe1.noarch.rpm",
          "jetty-jspc-maven-plugin-9.4.15-7.oe1.noarch.rpm",
          "jetty-http2-hpack-9.4.15-7.oe1.noarch.rpm",
          "jetty-annotations-9.4.15-7.oe1.noarch.rpm",
          "jetty-jsp-9.4.15-7.oe1.noarch.rpm",
          "jetty-alpn-client-9.4.15-7.oe1.noarch.rpm",
          "jetty-9.4.15-7.oe1.noarch.rpm",
          "jetty-client-9.4.15-7.oe1.noarch.rpm",
          "jetty-http2-server-9.4.15-7.oe1.noarch.rpm",
          "jetty-jaspi-9.4.15-7.oe1.noarch.rpm",
          "jetty-quickstart-9.4.15-7.oe1.noarch.rpm",
          "jetty-alpn-server-9.4.15-7.oe1.noarch.rpm",
          "jetty-security-9.4.15-7.oe1.noarch.rpm"
        ],
        "src": [
          "jetty-9.4.15-7.oe1.src.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP1",
        "name": "jetty",
        "purl": "pkg:rpm/openEuler/jetty\u0026distro=openEuler-20.03-LTS-SP1"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "9.4.15-7.oe1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "%global desc \\ 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. %{desc} %global extdesc %{desc}\\ \\ This package contains\r\n\r\nSecurity Fix(es):\r\n\r\nIn Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of \u201cquality\u201d (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values.(CVE-2020-27223)\r\n\r\nIn Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.(CVE-2021-28165)",
  "id": "OESA-2021-1166",
  "modified": "2026-08-06T11:04:24Z",
  "published": "2021-05-06T11:04:24Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1166"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-27223"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-28165"
    }
  ],
  "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-2020-27223",
    "CVE-2021-28165"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    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.