Categories
CVE-2021-28164

Information Disclosure in org.eclipse.jetty:jetty-webapp (CVE-2021-28164)

Summary

Vulnerability in org.eclipse.jetty:jetty-webapp (CVE-2021-28164). Risk of unauthorized operations or information disclosure. Exploitable via web.xml. Mitigation: upgrade to 9.4.39 or later.

Original description

The description as published by the source.

Release 9.4.37 introduced a more precise implementation of RFC3986 with regards to URI decoding, together with some new compliance modes to optionally allow support of some URI that may have ambiguous interpretation within the Servlet specified API methods behaviours. The default mode allowed % encoded . characters to be excluded for URI normalisation, which is correct by the RFC, but is not assumed by common Servlet implementations. The default compliance mode allows requests with URIs that contain %2e or %2e%2e segments to access protected resources within the WEB-INF directory. For example a request to /context/%2e/WEB-INF/web.xml can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application. Workarounds found by HttpCompliance mode RFC7230_NO_AMBIGUOUS_URIS can be enabled by updating start.d/http.ini to include: jetty.http.compliance=RFC7230_NO_AMBIGUOUS_URIS.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-28164 has been found in org.eclipse.jetty:jetty-webapp.
Attackers can target a specific entry point like web.xml over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.eclipse.jetty:jetty-webapp to 9.4.39 or later.
If unsure, ask your IT team or search "org.eclipse.jetty:jetty-webapp CVE-2021-28164" on the vendor's site.

CVE-2021-28164 (org.eclipse.jetty:jetty-webapp) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: web.xml
Patched: 9.4.39 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in org.eclipse.jetty:jetty-webapp. Attackers reach the vulnerable code path via web.xml without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.eclipse.jetty:jetty-webapp. Attack surface: web.xml.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 9.4.39.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.eclipse.jetty:jetty-webapp を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.eclipse.jetty:jetty-webapp to 9.4.39

    ステージング環境で 9.4.39 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven org.eclipse.jetty:jetty-webapp
[{"type":"ECOSYSTEM","events":[{"introduced":"9.4.37"},{"fixed":"9.4.39"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details