Skip to content
Fencer Vulns
medium 5.3

CVE-2021-34429 json

Encoded URIs can access WEB-INF directory in Eclipse Jetty

published 2021-07-15 5 y ago modified 2026-09-10 1 mo ago also GHSA-vjv5-gp2w-65vm , EUVD-2021-1493

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
99.3%
EPSS 99.3% chance of exploitation in 30 days, percentile 99.9%
public exploits
2
Metasploit, Exploit-DB, plus a Nuclei check

Summary

For 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 content of the WEB-INF directory and/or bypass some security constraints. This is a variation of the vulnerability reported in CVE-2021-28164/GHSA-v7ff-8wcx-gmc5.

Patch / fix

  • maven org.eclipse.jetty:jetty-webapp 9.4.43, 10.0.6, 11.0.6
  • eclipse jetty 9.4.43, 10.0.6, 11.0.6
  • oracle rest_data_services 22.1.1
  • oracle stream_analytics 19.1.0.0.6.4
  • jetty9 Debian 14, Debian 13, Debian 12 9.4.39-3

debian advisories DEBIAN-CVE-2021-34429

  • jetty-minimal SLE Module for Development Tools 15 SP3, SLE Module for Development Tools 15 SP2 9.4.43-3.12.2

suse advisories SUSE-SU-2021:2838-1

  • jetty-minimal openSUSE Leap 15.3 9.4.43-3.12.2
  • jetty-websocket openSUSE Leap 15.3 9.4.43-3.12.2

opensuse advisories openSUSE-SU-2021:2838-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-34429 updated cvss 5.3

jetty: crafted URIs allow bypassing security constraints

  • Red Hat Enterprise Linux 7 jetty-io, jetty-ant, jetty-jmx, jetty-jsp, jetty-xml, jetty-http, +30 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 jetty-io, jetty-http, jetty-util, jetty-server, jetty-servlet, jetty-security, +1 more
    affected: no fix planned “Will not fix”
  • Red Hat JBoss A-MQ 6 jetty-server Red Hat JBoss Fuse 6 jetty, jetty-server Red Hat OpenShift Container Platform 3.11 jenkins
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Container Platform 4 jenkins
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 10 (Newton) opendaylight Red Hat OpenStack Platform 13 (Queens) opendaylight
    affected: no fix planned “Out of support scope”
  • Red Hat AMQ 7.9.0
    fixed: vendor fix RHSA-2021:3700
  • Red Hat AMQ Streams 2.0.0
    fixed: vendor fix RHSA-2022:0138
  • Red Hat Fuse 7 jetty Red Hat Integration Camel K 1 jetty Red Hat Integration Camel Quarkus 1 jetty Red Hat Integration Service Registry jetty-server Red Hat JBoss Data Grid 7 jetty-server Red Hat OpenShift Container Platform 4 openshift4/ose-metering-hive, openshift4/ose-metering-hadoop, openshift4/ose-metering-presto
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (Metasploit auxiliary/gather/jetty_web_inf_disclosure)
  2. Published

Exploit prediction

99.33% chance of exploitation in the next 30 days, higher than 99.9% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.eclipse.jetty:jetty-webapp
>=9.4.37, <9.4.43
>=10.0.1, <10.0.6
>=11.0.1, <11.0.6
9.4.43
10.0.6
11.0.6

Affected products

  • The Eclipse Foundation Eclipse Jetty

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-551 Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
  • CWE-863 Incorrect Authorization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.