LiveActive security incident?Get immediate response
CVE Record

CVE-2020-17104: Visual Studio Code JSHint Extension Remote Code Execution Vulnerability

Visual Studio Code JSHint Extension Remote Code Execution Vulnerability

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes remote code execution in the Visual Studio Code JSHint extension. Successful exploitation could let code run with the privileges of the user running VS Code, affecting confidentiality, integrity, and availability. The source bundle does not provide trigger details or confirm active exploitation.

Executive priority

Prioritize remediation for developer workstations because compromise could affect source code, credentials, and build workflows. Treat as high priority, but not an emergency unless internal exposure or vendor intelligence indicates exploitation.

Technical view

CVE-2020-17104 is rated high with CVSS 3.1 score 7.8. The vector is local, low complexity, no privileges required, and user interaction required. Impact is high across confidentiality, integrity, and availability. The bundle lists Microsoft Visual Studio Code/JSHint extension context and references MSRC guidance.

Likely exposure

Exposure is most likely on developer workstations where the affected Visual Studio Code/JSHint extension is installed. The provided data lists version 1.0.0 but does not include full version-range detail beyond the source metadata.

Exploitation context

CISA KEV is false, and the supplied sources do not state active exploitation. CVSS indicates exploitation requires local context and user interaction, with no privileges required. Exact triggering conditions are not described in the source bundle.

Researcher notes

The bundle lacks CWE, detailed vulnerable code path, exploit narrative, and exact remediation version. Analysis should stay anchored to MSRC and CVE records. Further validation should focus on installed extension presence, version evidence, and vendor advisory details.

Mitigation direction

  • Review Microsoft MSRC guidance for CVE-2020-17104.
  • Apply the vendor-supported update or removal guidance.
  • Inventory developer endpoints for VS Code and the JSHint extension.
  • Disable or remove affected extension installations pending vendor guidance.

Validation and detection

  • Check endpoint software inventory for VS Code and the JSHint extension.
  • Confirm installed extension versions against Microsoft advisory guidance.
  • Verify remediation through endpoint management or extension inventory records.
  • Document any remaining affected developer systems and owner follow-up.
Prepared
Confidence
medium
Sources
3

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-17104 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
0Timeline events
0ADP providers
2Source 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.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2020-17104Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftVisual Studio Code1.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.