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

Vulnerability in eventlet (CVE-2021-21419)

Summary

Vulnerability in eventlet (CVE-2021-21419). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.31.0 or later.

Original description

The description as published by the source.

Impact

A websocket peer may exhaust memory on Eventlet side by sending very large websocket frames. Malicious peer may exhaust memory on Eventlet side by sending highly compressed data frame.

Patches

Version 0.31.0 restricts websocket frame to reasonable limits.

Workarounds

Restricting memory usage via OS limits would help against overall machine exhaustion. No workaround to protect Eventlet process.

For more information

If you have any questions or comments about this advisory:

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

CVE-2021-21419 (eventlet) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.31.0 — apply immediately
Workaround: Restricting memory usage via OS limits would help against overall machine exhaustion.
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-400) exists in eventlet.

📍 Affected scope

Check the vendor advisory for the affected versions of eventlet.

🔥 Severity

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

🔧 How to fix

Update to 0.31.0.

🛡️ Workaround

Workaround: Restricting memory usage via OS limits would help against overall machine exhaustion.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'eventlet' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    grep -r 'eventlet' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で eventlet を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Restricting memory usage via OS limits would help against overall machine exhaustion.

    パッチが適用されるまでの応急処置として、Restricting memory usage via OS limits would help against overall machine exhaustion. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade eventlet to 0.31.0

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

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

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

Affected packages

PyPI eventlet
[{"type":"ECOSYSTEM","events":[{"introduced":"0.10"},{"fixed":"0.31.0"}]}]

References

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