LiveActive security incident?Get immediate response
CVE Record

CVE-2020-17150: Visual Studio Code Remote Code Execution Vulnerability

Visual Studio Code Remote Code Execution Vulnerability

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a high-severity remote code execution flaw in Microsoft’s Visual Studio Code TS-Lint Extension version 1.0.0. Successful exploitation could let attacker-controlled code run with serious confidentiality, integrity, and availability impact. The provided sources do not describe the exact trigger path.

Executive priority

Prioritize remediation for engineering environments because developer tools can become a route into source code, credentials, and build workflows. Urgency is high, but the available evidence does not show active exploitation.

Technical view

CVE-2020-17150 affects Visual Studio Code TS-Lint Extension 1.0.0. CVSS 3.1 is 7.8 with local attack vector, low complexity, no privileges required, user interaction required, and high impact across confidentiality, integrity, and availability. MSRC lists an official remediation.

Likely exposure

Exposure is most likely on developer workstations, build images, or managed development environments that still have Visual Studio Code TS-Lint Extension 1.0.0 installed. Systems without that extension version are not shown as affected by the supplied sources.

Exploitation context

The source bundle shows no CISA KEV listing and CVSS exploit maturity is unproven. Treat exploitation as plausible because the impact is code execution, but do not claim active exploitation from the provided evidence.

Researcher notes

Key constraints are local attack vector and required user interaction. The provided sources identify one affected product/version and an official Microsoft remediation, but do not include CWE, exploit details, or a named fixed version in the bundle.

Mitigation direction

  • Follow MSRC guidance for CVE-2020-17150.
  • Update the affected extension where Microsoft provides a fixed version.
  • Remove TS-Lint Extension 1.0.0 if update status cannot be verified.
  • Prioritize managed developer endpoints and shared development images.
  • Track remediation through endpoint or software inventory tooling.

Validation and detection

  • Inventory Visual Studio Code extensions across developer endpoints.
  • Confirm no installation reports TS-Lint Extension version 1.0.0.
  • Review golden images and CI development containers for the extension.
  • Verify remediation evidence against the MSRC CVE record.
  • Document any exception with owner, scope, and review date.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-17150 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2020-17150Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftVisual Studio Code TS-Lint Extension1.0.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.