Code execution via improper resource-name restriction
Published Jun 11, 2024 · Updated Aug 10, 2026
Remote code execution in Microsoft Windows DFS allows local users with low-privileged code execution to run code after user interaction. Microsoft has not disclosed the affected DFS resource-name handling locus or the incorrect operation performed on attacker-controlled input. Exploitation requires prior low-privileged code execution on the target and an adjacent position, and it affects confidentiality and integrity without a reported service interruption.
Summary
What happened
Remote code execution in Microsoft Windows DFS allows local users with low-privileged code execution to run code after user interaction. Microsoft has not disclosed the affected DFS resource-name handling locus or the incorrect operation performed on attacker-controlled input. Exploitation requires prior low-privileged code execution on the target and an adjacent position, and it affects confidentiality and integrity without a reported service interruption.
The record
- CVE
- CVE-2024-30063
- Published
- Jun 11, 2024
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-641
- Attack vector
- adjacent
- Privileges
- authenticated
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=10.0.10240.0 <10.0.10240.20680
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.
Weakness, pattern, technique
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