LiveActive security incident?Get immediate response
CVE Record

CVE-2024-30075: Windows Link Layer Topology Discovery Protocol Remote Code Execution Vulnerability

Windows Link Layer Topology Discovery Protocol Remote Code Execution Vulnerability

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-30075 is a high-severity flaw in Windows Link Layer Topology Discovery Protocol. An attacker on an adjacent network could potentially execute code after user interaction, threatening system confidentiality, integrity, and availability. The supplied affected list identifies specific Windows Server 2008 and 2008 R2 SP1 installations.

Executive priority

Prioritize remediation promptly, especially where listed legacy servers share network segments with untrusted or broadly accessible devices. The potential impact is complete compromise, although exploitation requires adjacency and user interaction. Escalate unsupported or difficult-to-update systems for isolation or replacement planning.

Technical view

The vulnerability is classified as CWE-122, a heap-based buffer overflow, with CVSS 3.1 score 8.0. Its vector indicates adjacent-network access, low attack complexity, no privileges, required user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on the listed Windows Server 2008 SP2 and Windows Server 2008 R2 SP1 builds, including Server Core installations. The adjacent-network requirement limits reach compared with an internet-routable flaw, but reachable systems may remain at substantial risk.

Exploitation context

The bundle does not identify this CVE as a CISA KEV and provides no evidence of active exploitation. The CVSS vector records exploit maturity as unproven and requires user interaction. Treat exploitation status as unconfirmed, not impossible.

Researcher notes

The supplied evidence establishes the affected products, CWE, severity, access conditions, user-interaction requirement, and vendor advisory. It does not provide vulnerable component internals, triggering mechanics, specific update identifiers, observed attacks, or confirmed exploit availability. Those points should not be inferred.

Mitigation direction

  • Inventory the specifically listed Windows Server 2008 and 2008 R2 installations.
  • Apply the applicable Microsoft security update referenced by the vendor advisory.
  • Check Microsoft guidance for prerequisites, supported update paths, and deployment considerations.
  • Restrict untrusted access from adjacent network segments until affected systems are remediated.

Validation and detection

  • Confirm whether listed operating-system versions and Server Core variants exist in the environment.
  • Verify the applicable Microsoft security update is installed successfully on each affected host.
  • Confirm affected hosts are not reachable from untrusted adjacent network segments.
  • Recheck Microsoft’s advisory for revised affected-product or remediation information.
Prepared
Confidence
high
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.

cwe · low confidence lookup

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 lookup
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-2024-30075 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
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: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
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

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
8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.15.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

8High
CVSS 3.1 vector shape for CVE-2024-30075Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0Listed
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0Listed
MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)6.0.6003.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

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.