cbcvebase.
CVE-2020-1171
published 2020-05-21

CVE-2020-1171: A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads configuration files after opening a project, aka 'Visual…

PriorityP355high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
14.27%
96.2th percentile
A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads configuration files after opening a project, aka 'Visual Studio Code Python Extension Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1192.

Affected

3 ranges
VendorProductVersion rangeFixed in
microsoftpython< 2020.5.02020.5.0
microsoftvisual_studio_code
msrcpython_extension_for_visual_studio_code

Detection & IOCsextracted from sources · hover to see the quote

  • Attacker must convince a target to clone a repository and open it in Visual Studio Code with the Python extension installed — monitor for suspicious repository clones followed by VS Code project opens with the Python extension active.
  • Malicious code execution is triggered when the integrated terminal is opened in VS Code after loading attacker-controlled configuration files — alert on unexpected process spawns from VS Code's integrated terminal (e.g., code.exe or its child processes spawning shells/interpreters).
  • The attack vector is malicious configuration files loaded by the Python extension upon project open — inspect cloned repositories for suspicious Python environment configuration files (e.g., .env, pyrightconfig.json, settings.json) that set unexpected environment variables.
  • The root cause is improper handling of environment variables by the VS Code Python extension — monitor for environment variable injection patterns in workspace-level configuration files within cloned repositories.
  • ·Exploitation requires the target to have the VS Code Python extension installed; without it, the vulnerability is not triggerable.
  • ·This CVE is distinct from CVE-2020-1192, which is a separate but related VS Code Python extension RCE vulnerability — ensure detections and patches address both.
  • ·Impact is scoped to the current user's context; if the user has administrative rights, full system compromise is possible.

CVSS provenance

nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.09.3CRITICALAV:N/AC:M/Au:N/C:C/I:C/A:C
vendor_msrc8.8HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.