LiveActive security incident?Get immediate response
CVE Record

CVE-2021-34479: Microsoft Visual Studio Spoofing Vulnerability

Microsoft Visual Studio Spoofing Vulnerability

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Microsoft Visual Studio/Visual Studio Code spoofing vulnerability with high impact scoring. The source bundle indicates local access and user interaction are required, but successful exploitation could affect confidentiality, integrity, and availability. Active exploitation is not established by the supplied KEV status.

Executive priority

Treat this as a high-priority workstation remediation item, especially for developer environments. It is not KEV-backed in the supplied data, but the potential impact is broad if the vulnerable software is present and user interaction occurs.

Technical view

CVE-2021-34479 is rated CVSS 7.8 with AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. The supplied affected data lists Microsoft Visual Studio Code 1.0.0 and a Visual Studio Code CPE. The description is sparse, so exact spoofing mechanics and affected-version boundaries need vendor confirmation.

Likely exposure

Exposure is most relevant where Microsoft Visual Studio Code matching the supplied affected data exists on endpoints. Because the bundle’s product details are limited, vulnerability managers should validate installed versions against Microsoft’s advisory rather than relying only on the CPE entry.

Exploitation context

The vector indicates local exploitation with required user interaction and no privileges required. Exploit maturity is listed as unproven, and the CVE is not marked KEV in the bundle, so public active exploitation is not evidenced here.

Researcher notes

The supplied record lacks detailed root cause, attack scenario, and precise fixed-version information. The CVSS vector supports local, user-assisted exploitation with high CIA impact. Validate applicability directly against MSRC before writing detections or exposure reports.

Mitigation direction

  • Review Microsoft’s MSRC advisory for official remediation and affected-version details.
  • Update affected Microsoft Visual Studio Code installations per vendor guidance.
  • Prioritize developer workstations and shared engineering endpoints for inventory checks.
  • Use endpoint management to confirm vulnerable versions are removed.
  • Monitor Microsoft guidance for any corrected affected-product scope.

Validation and detection

  • Inventory Microsoft Visual Studio Code installations and versions across managed endpoints.
  • Compare discovered versions against the MSRC advisory for CVE-2021-34479.
  • Check whether remediation status aligns with Microsoft’s official release guidance.
  • Confirm endpoint management reports no remaining vulnerable installations.
  • Document any exceptions where vendor applicability remains unclear.
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.

cve · low confidence lookup

CVE-2021-34479 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-2021-34479Attack 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.