cve.bz

CVE-2024-49076 microsoft: Improper Authentication

7.8 highEPSS 1.2%

High (7.8) in microsoft. EPSS 1.2% estimated probability of exploitation activity in the next 30 days.

On this page
Windows Virtualization-Based Security (VBS) Enclave Elevation of Privilege Vulnerability

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.2% (unchanged from 1.2% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 69th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-01-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-49076 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-49076?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-49076?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-49076 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.6659
Microsoft Windows 10 Version 21H2from 10.0.19043.0 before 10.0.19044.5247
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.5247
Microsoft Windows 11 version 22H2from 10.0.22621.0 before 10.0.22621.4602
Microsoft Windows 11 version 22H3from 10.0.22631.0 before 10.0.22631.4602
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.4602
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.2605
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.6659
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.6659
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.2966
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)from 10.0.25398.0 before 10.0.25398.1308
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.2605
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.2605

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON