Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2024-47821

OS Command Injection in pyload-ng (CVE-2024-47821)

Summary

OS command injection in pyload-ng (CVE-2024-47821). Successful exploitation can lead to full system takeover. Exploitable via `Referer header`. Mitigation: upgrade to `0.5.0b3.dev87` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-47821** has been found in pyload-ng. Attackers can target a specific entry point like `Referer header` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: ?/10. What to do: upgrade pyload-ng to **0.5.0b3.dev87** or later. If unsure, ask your IT team or search "pyload-ng CVE-2024-47821" on the vendor's site.
CVE-2024-47821 (pyload-ng) — CWE-78 / Attack vector: remote (network-reachable) / no user interaction Attack surface: Referer header / Host header / `flashgot` / `download_finished` Patched: `0.5.0b3.dev87` — 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
**OS command injection** (CWE-78) exists in pyload-ng. Attackers reach the vulnerable code path via `Referer header` without authentication.
📍 Affected scope
pyload-ng — . Attack surface: Referer header / Host header / `flashgot` / `download_finished`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.5.0b3.dev87**.
🛡️ 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. Run `grep -r 'pyload-ng' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

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

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

  2. 6
    Apply patch patch 
    Upgrade pyload-ng to 0.5.0b3.dev87

    ステージング環境で 0.5.0b3.dev87 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

PyPI pyload-ng
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.0b3.dev87"}]}]
pip pyload-ng
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.0b3.dev87"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →