← Back
CVE-2024-5023
Command Injection in consoleme (CVE-2024-5023)
Summary
command injection in consoleme (CVE-2024-5023). Confidential information can be exposed externally. Exploitable via ``cache_resource_templates.repositories``. Mitigation: upgrade to `1.4.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-5023** has been found in consoleme.
Attackers can target a specific entry point like ``cache_resource_templates.repositories`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade consoleme to **1.4.0** or later.
If unsure, ask your IT team or search "consoleme CVE-2024-5023" on the vendor's site.
CVE-2024-5023 (consoleme) — CWE-77 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `cache_resource_templates.repositories`
Patched: `1.4.0` — 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-77) exists in consoleme. Attackers reach the vulnerable code path via ``cache_resource_templates.repositories`` without authentication.
📍 Affected scope
consoleme — . Attack surface: `cache_resource_templates.repositories`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.4.0**.
🛡️ 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 'consoleme' .` 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
-
1Identify exposure identify
grep -r 'consoleme' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `consoleme` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade consoleme to 1.4.0ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
consoleme
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-5023
- advisory https://github.com/advisories/GHSA-3783-62vc-jr7x
- package https://github.com/Netflix/consoleme
- package https://pypi.org/project/consoleme
- web https://github.com/Netflix/consoleme/security/advisories/GHSA-3783-62vc-jr7x
- web https://github.com/Netflix/consoleme/pull/9380
- web https://github.com/Netflix/consoleme/commit/2795a2bd553938a21c0643b37452971625ce67f5
- web https://github.com/Netflix/security-bulletins/blob/master/advisories/nflx-2024-002.md