Categories
CVE-2019-10799

OS Command Injection in compile-sass (CVE-2019-10799)

Summary

OS command injection in compile-sass (CVE-2019-10799). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.0.5 or later.

Original description

The description as published by the source.

compile-sass prior to 1.0.5 allows execution of arbritary commands. The function "setupCleanupOnExit(cssPath)" within "dist/index.js" is executed as part of the "rm" command without any sanitization.

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-2019-10799 has been found in compile-sass.
Successful exploitation can lead to full system takeover.
What to do: upgrade compile-sass to 1.0.5 or later.
If unsure, ask your IT team or search "compile-sass CVE-2019-10799" on the vendor's site.

CVE-2019-10799 (compile-sass) — CWE-78
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.0.5 — 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 compile-sass.

📍 Affected scope

Check the vendor advisory for the affected versions of compile-sass.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.0.5.

🛡️ 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 'compile-sass' . 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 'compile-sass' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade compile-sass to 1.0.5

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

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

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

Affected packages

npm compile-sass
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.0.5"}]}]

References

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