dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-9145

HIGH · 7.1 CVSS v4.0 Published 2024-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
No privileges

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
Wiz Code Visual Studio Code extension in versions 1.0.0 up to 1.5.3 and Wiz (legacy) Visual Studio Code extension in versions 0.13.0 up to 0.17.8 are vulnerable to local command injection if the user opens a maliciously crafted Dockerfile located in a path that has been marked as a "trusted folder" within Visual Studio Code, and initiates a manual scan of the file.

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 · high confidence

The Wiz Code and Wiz (legacy) Visual Studio Code extensions are vulnerable to local command injection when processing Dockerfiles. An attacker can craft a malicious Dockerfile containing embedded commands that get executed when a user, who has marked a folder as 'trusted' in VS Code, manually initiates a scan of the file. The vulnerability stems from insufficient sanitization of Dockerfile content before passing it to system command execution.

MitigationUsers should update to the latest version of the Wiz Code extension (beyond 1.5.3) or Wiz legacy extension (beyond 0.17.8). Until patched, avoid manually scanning Dockerfiles from untrusted sources, even in VS Code trusted folders.

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
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/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 installed Wiz extension version
    In VS Code, go to Extensions panel, search for 'Wiz Code' or 'Wiz' (legacy), and check the installed version number in the extension details
    Affected if Version is 1.5.3 or earlier for Wiz Code, or 0.17.8 or earlier for the legacy extension
  2. Verify Dockerfiles exist in trusted workspace
    Check VS Code workspaces marked as 'Trusted' (look for .dockerfile, Dockerfile, Dockerfile.* files in the workspace folder)
    Affected if Dockerfiles are present in any folder that VS Code considers trusted
  3. Confirm manual scan capability is present
    Open a Dockerfile in a trusted workspace, right-click and look for Wiz scan options (such as 'Scan with Wiz' or similar) in the context menu
    Affected if Wiz scan options appear in the context menu when right-clicking a Dockerfile in a trusted folder
  4. Check if any Dockerfiles were recently opened or scanned
    Review VS Code recent activity, file history, or Wiz extension logs to see if Dockerfiles were accessed in trusted workspaces
    Affected if Dockerfiles in trusted folders have been opened or scanned recently

A user is affected if they have Wiz Code <=1.5.3 or Wiz legacy <=0.17.8 installed, have marked a folder as trusted in VS Code, and have Dockerfiles present that could be manually scanned.

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

Users should update to the latest version of the Wiz Code extension (beyond 1.5.3) or Wiz legacy extension (beyond 0.17.8). Until patched, avoid manually scanning Dockerfiles from untrusted sources, even in VS Code trusted folders.

Recommended fix Moderate confidence

Wiz Code: version 1.5.4 or later; Wiz (legacy): version 0.17.9 or later

  1. Open Visual Studio Code
  2. Navigate to the Extensions view (Ctrl+Shift+X or Cmd+Shift+X)
  3. Search for 'Wiz Code' or 'Wiz (legacy)' extension
  4. Click on the extension and check the version number
  5. If running version 1.0.0 to 1.5.3 of Wiz Code, update to version 1.5.4 or later
  6. If running version 0.13.0 to 0.17.8 of Wiz (legacy), update to version 0.17.9 or later
  7. Restart Visual Studio Code after the update
  8. Avoid opening untrusted Dockerfiles in VS Code trusted folders as a defense-in-depth measure
Caveat No known breaking changes; this is a security patch release

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9145 — 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-9145 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