Code execution via LLTD heap buffer overflow
Published Jun 11, 2024 · Updated Aug 10, 2026
Heap-based buffer overflow in Microsoft Windows Server 2008 SP2 and 2008 R2 SP1 allows attackers to execute code over an adjacent network. Microsoft identifies the locus as the Link Layer Topology Discovery Protocol but has not disclosed the malformed input or faulty memory operation that overruns the heap. Exploitation requires user interaction and adjacent-network access; success runs attacker-controlled code with the affected service's privileges.
Summary
What happened
Heap-based buffer overflow in Microsoft Windows Server 2008 SP2 and 2008 R2 SP1 allows attackers to execute code over an adjacent network. Microsoft identifies the locus as the Link Layer Topology Discovery Protocol but has not disclosed the malformed input or faulty memory operation that overruns the heap. Exploitation requires user interaction and adjacent-network access; success runs attacker-controlled code with the affected service's privileges.
The record
- CVE
- CVE-2024-30074
- Published
- Jun 11, 2024
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2008 R2 Service Pack 1
- Classifications
- CWE-122, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2024CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.1.7601.0 <6.1.7601.27170
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo