CVE-2021-28165: 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 inva

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• eclipse jetty7.2.2 and later · before 9.4.39
• eclipse jetty10.0.0 and later · before 10.0.2
• eclipse jetty11.0.0 and later · before 11.0.2
• jenkins jenkinsbefore 2.286
• jenkins jenkinsbefore 2.277.3
• netapp cloud managerbefore 3.9.8
• netapp e-series performance analyzerbefore 3.0
• netapp e-series santricity os controller11.0.0 and later · before 11.70.1
• netapp e-series santricity storagebefore 1.10
• netapp e-series santricity web servicesbefore 5.1
• netapp ontap toolsbefore 9.10
• netapp santricity cloud connectorall versions
• netapp santricity web services proxybefore 5.1
• netapp snapcenterbefore 4.6
• netapp storage replication adapter for clustered data ontapbefore 9.10
• netapp vasa provider for clustered data ontapbefore 9.10
• oracle autovue for agile product lifecycle management21.0.2
• oracle communications cloud native core policy1.14.0
• oracle communications element manager8.2.2
• oracle communications services gatekeeper7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (eclipse). Independent of NVD's CPE analysis and usually ahead of it.

• The Eclipse Foundation Eclipse Jetty

  • 7.2.2 and later · before unspecifiedaffected
  • unspecified and later · up to and including 9.4.38affected
  • 10.0.0.alpha0 and later · before unspecifiedaffected
  • unspecified and later · up to and including 10.0.1affected
  • 11.0.0.alpha0 and later · before unspecifiedaffected
  • unspecified and later · up to and including 11.0.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2021-34429For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the con
  60This week
• CVE-2021-28164In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segm
  60This week
• CVE-2015-2080The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process mem
  53Plan

Published before and after this one in the same product

• ← EarlierCVE-2020-27223Feb 26, 2021 · 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
  44Plan
• ← EarlierCVE-2021-28163Apr 1, 2021 · In Eclipse Jetty 9.4.32 to 9.4.38, 10.0.0.beta2 to 10.0.1, and 11.0.0.beta2 to 11.0.1, if a user uses a webapps directory that is a symlink,
  11Monitor
• Later →CVE-2021-28169Jun 8, 2021 · For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to a
  45Plan

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1function expand(node) {2  return node.children.map(expand);3}

1const MAX_DEPTH = 32;2function expand(node, depth = 0) {3  if (depth > MAX_DEPTH) throw new Error("too deep");4  return node.children.map((c) => expand(c, depth + 1));5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.