Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2021-28163

Information Disclosure in org.eclipse.jetty:jetty-deploy (CVE-2021-28163)

Summary

Vulnerability in org.eclipse.jetty:jetty-deploy (CVE-2021-28163). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 11.0.2 or later.

Original description

The description as published by the source.

Impact

If the ${jetty.base} directory or the ${jetty.base}/webapps directory is a symlink (soft link in Linux), the contents of the ${jetty.base}/webapps directory may be deployed as a static web application, exposing the content of the directory for download.

For example, the problem manifests in the following ${jetty.base}:

demo-base/
├── etc
├── lib
├── resources
├── start.d
├── deploy
│   └── async-rest.war
└── webapps -> deploy

Workarounds

Do not use a symlink

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-28163 has been found in org.eclipse.jetty:jetty-deploy.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.eclipse.jetty:jetty-deploy to 11.0.2 or later.
If unsure, ask your IT team or search "org.eclipse.jetty:jetty-deploy CVE-2021-28163" on the vendor's site.

CVE-2021-28163 (org.eclipse.jetty:jetty-deploy) — CWE-200
Attack vector: remote (network-reachable) / no user interaction
Patched: 11.0.2 — 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-deploy.

📍 Affected scope

Check the vendor advisory for the affected versions of org.eclipse.jetty:jetty-deploy.

🔥 Severity

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

🔧 How to fix

Update to 11.0.2.

🛡️ 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-deploy を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.eclipse.jetty:jetty-deploy to 11.0.2

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

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

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

Affected packages

Maven org.eclipse.jetty:jetty-deploy
[{"type":"ECOSYSTEM","events":[{"introduced":"11.0.0"},{"fixed":"11.0.2"}]}]

References

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