dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-5023

CRITICAL · 9.3 CVSS v4.0 Published 2024-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Netflix ConsoleMe allows Command Injection.This issue affects ConsoleMe: before 1.4.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Netflix ConsoleMe contains a command injection vulnerability allowing attackers to execute arbitrary commands due to improper neutralization of special elements in command processing. This critical flaw (CVSS 9.3) affects all versions prior to 1.4.0.

MitigationUpgrade ConsoleMe to version 1.4.0 or later to address the command injection vulnerability. If immediate upgrade is not possible, restrict network access to the ConsoleMe interface and audit for any unauthorized command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ConsoleMe installation
    Check for ConsoleMe in your environment by looking for the consoleme binary, checking running processes (ps aux | grep consoleme), or searching for consoleme in installed packages (pip list, npm list, etc.)
    Affected if ConsoleMe is present in the environment
  2. Determine installed ConsoleMe version
    Run the version command for ConsoleMe (consoleme --version) or check the version in package management (pip show consoleme, requirements.txt, package.json)
    Affected if The installed version cannot be determined or is shown as below 1.4.0
  3. Compare version to affected range
    Verify the installed version against the affected range: any version prior to 1.4.0 is vulnerable
    Affected if The installed version is below 1.4.0 (e.g., 1.3.x, 1.2.x, 1.1.x, 1.0.x, or any pre-1.4.0 release)
  4. Check for command processing features
    Review ConsoleMe configuration files and settings for features that process commands or interact with system shells - look for settings related to command execution, shell invocation, or external command processing
    Affected if Command processing features are enabled and the version is below 1.4.0

You are affected if ConsoleMe is installed and the version is any release prior to 1.4.0, as all earlier versions contain the command injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ConsoleMe to version 1.4.0 or later to address the command injection vulnerability. If immediate upgrade is not possible, restrict network access to the ConsoleMe interface and audit for any unauthorized command execution.

Recommended fix Moderate confidence

1.4.0

  1. Check current ConsoleMe version using the installed package or Docker image tag
  2. Stop the ConsoleMe service
  3. Backup current configuration files (typically in /etc/consoleme/ or the config directory)
  4. Upgrade ConsoleMe to version 1.4.0 using the appropriate method (pip install --upgrade consoleme==1.4.0, Docker, or repository update)
  5. Review configuration files for any required updates between versions
  6. Start the ConsoleMe service
  7. Verify the upgrade was successful by checking the version and ensuring the service runs without errors

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5023 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data