Security readout for executives and security teams
Plain-English summary
CVE-2024-30092 is a high-severity Windows Hyper-V remote code execution vulnerability. It affects many supported Windows client and server releases. Microsoft lists an official fix. The available bundle does not show known active exploitation or CISA KEV listing, but successful exploitation could compromise confidentiality, integrity, and availability of Hyper-V systems.
Executive priority
Prioritize remediation in normal high-severity patch cycles, faster for production Hyper-V hosts or shared virtualization infrastructure. The business risk is high because successful exploitation could enable full compromise of affected virtualization systems, but current supplied evidence does not indicate active exploitation.
Technical view
The CVSS 3.1 vector is 8.0: adjacent attack vector, high complexity, low privileges required, no user interaction, changed scope, and high CIA impact. The weaknesses are CWE-20 and CWE-829. Affected products include Windows 10, Windows 11, Windows Server 2016, 2019, 2022, and Server Core variants.
Likely exposure
Exposure is most relevant to organizations running Hyper-V on affected Windows client or server builds, including virtualization hosts and Server Core deployments. Systems not using Hyper-V may have lower practical exposure, but the source bundle does not provide feature-state conditions.
Exploitation context
The provided CVSS says exploitation requires adjacent access, low privileges, and high complexity, with no user interaction. Microsoft marks exploit code maturity as unproven in the supplied vector, and the bundle says CISA KEV is false. No cited source here supports active exploitation.
Researcher notes
Key constraints are AV:A, AC:H, PR:L, UI:N, and changed scope. Research should focus on Hyper-V-enabled affected builds, patch presence, and whether adjacent attacker paths exist. Do not assume internet-routable exploitation from the provided vector alone.
Mitigation direction
- Apply Microsoft’s official update for CVE-2024-30092.
- Prioritize Hyper-V hosts running listed Windows Server and client versions.
- Check MSRC for product-specific update packages and supersedence.
- If patching is delayed, treat affected Hyper-V hosts as high-risk assets.
Validation and detection
- Inventory Windows systems with Hyper-V enabled or hosting virtualization workloads.
- Compare OS versions against the affected product list in the source bundle.
- Verify the applicable Microsoft security update is installed.
- Confirm unsupported or unpatched builds are tracked for remediation.
- Document systems where Hyper-V exposure cannot be confirmed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-829: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution 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 lookupCVE-2024-30092 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C1.36microsoftVulnerability scoring details
Base CVSS 3.1 score
8HighVector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Windows Hyper-V Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.