Security readout for executives and security teams
Plain-English summary
A nearby network attacker could exploit a memory-handling flaw in affected legacy Windows Server systems to run malicious code after user interaction. Successful exploitation could compromise data, alter systems, or disrupt services. The flaw is serious, but the supplied evidence does not establish active exploitation.
Executive priority
Treat as a high-priority legacy-system remediation issue. Promptly identify affected servers and patch them, especially on shared or untrusted networks. It is not evidence of an internet-wide emergency because exploitation requires adjacent access and user interaction, and active exploitation is unconfirmed.
Technical view
CVE-2024-30074 is a CWE-122 heap-based buffer overflow in Windows Link Layer Topology Discovery Protocol. CVSS 3.1 rates it 8.0: adjacent-network access, low complexity, no privileges, user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited by adjacent-network access and required user interaction. The supplied affected list covers Windows Server 2008 SP2 and Server 2008 R2 SP1, including Server Core installations. No other Windows versions should be inferred from this bundle.
Exploitation context
The CVSS temporal vector reports proof-of-concept exploit maturity. However, the bundle provides no supporting exploit details, and the CVE is not identified as a CISA KEV entry. Active exploitation is therefore not established.
Researcher notes
The supplied scope identifies four legacy Windows Server product variants. Technical evidence is limited to the title, CVSS vector, CWE-122 classification, affected versions, and Microsoft advisory reference. Exact triggering behavior, required interaction, patch identifiers, and exploitation telemetry are not included and should not be inferred.
Mitigation direction
- Apply the Microsoft security update identified in the vendor advisory.
- Prioritize affected servers accessible from untrusted or broadly shared local networks.
- If patching is delayed, check Microsoft guidance for supported mitigations or workarounds.
- Restrict unnecessary network adjacency to affected legacy servers.
Validation and detection
- Inventory the specifically listed Windows Server versions and Server Core installations.
- Compare installed security updates with the Microsoft CVE advisory.
- Confirm potentially exposed servers are not unnecessarily reachable from untrusted adjacent networks.
- After remediation, verify update installation and review relevant security monitoring for anomalies.
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-122: 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-30074 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:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/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:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C2.15.9microsoftVulnerability scoring details
Base CVSS 3.1 score
8HighVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/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 Link Layer Topology Discovery Protocol 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.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.