Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-27218

Vulnerability in org.eclipse.jetty:jetty-server (CVE-2020-27218)

Summary

Vulnerability in org.eclipse.jetty:jetty-server (CVE-2020-27218). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.4.35.v20201120 or later.

Original description

The description as published by the source.

Impact

If GZIP request body inflation is enabled and requests from different clients are multiplexed onto a single connection and if an
attacker can send a request with a body that is received entirely by not consumed by the application, then a subsequent request
on the same connection will see that body prepended to it's body.

The attacker will not see any data, but may inject data into the body of the subsequent request

CVE score is 4.8 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L

Workarounds

The problem can be worked around by either:

  • Disabling compressed request body inflation by GzipHandler.
  • By always fully consuming the request content before sending a response.
  • By adding a Connection: close to any response where the servlet does not fully consume request content.

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

CVE-2020-27218 (org.eclipse.jetty:jetty-server) — CWE-226
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 9.4.35.v20201120 — 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

A vulnerability (CWE-226) exists in org.eclipse.jetty:jetty-server.

📍 Affected scope

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

🔥 Severity

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

🔧 How to fix

Update to 9.4.35.v20201120.

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

  2. 2
    Apply patch patch 
    Upgrade org.eclipse.jetty:jetty-server to 9.4.35.v20201120

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

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

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

Affected packages

Maven org.eclipse.jetty:jetty-server
[{"type":"ECOSYSTEM","events":[{"introduced":"9.4.0"},{"fixed":"9.4.35.v20201120"}]}]

References

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