Cyber Resilience

CVE-2024-30063

Microsoft Windows Server 2008 r2

Published
11 June 2024
Modified
20 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
EPSS Score 0.010 60th percentile
Risk Priority 52 floored blend · peak EPSS

Summary

CVE-2024-30063 is a medium-severity Improper Restriction of Names for Files and Other Resources (CWE-641) vulnerability in Microsoft Windows Server 2008. Its CVSS base score is 6.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Windows Distributed File System (DFS) Remote Code Execution Vulnerability

CWE(s)
CWE-641NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-25177Same product: Microsoft Windows 10 1607
CVE-2024-30073Same product: Microsoft Windows 10 1507
CVE-2024-38049Same product: Microsoft Windows 10 1507
CVE-2024-20652Same product: Microsoft Windows 10 1507
CVE-2025-21189Same product: Microsoft Windows 10 1507
CVE-2025-21268Same product: Microsoft Windows 10 1507
CVE-2025-21269Same product: Microsoft Windows 10 1507
CVE-2023-35384Same product: Microsoft Windows 10 1507
CVE-2024-30039Same product: Microsoft Windows 10 1507
CVE-2024-26176Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.20680
microsoft
windows 10 1607
≤ 10.0.14393.7070
microsoft
windows 10 1809
≤ 10.0.17763.5936
microsoft
windows 10 21h2
≤ 10.0.19044.4529
microsoft
windows 10 22h2
≤ 10.0.19045.4529
microsoft
windows 11 21h2
≤ 10.0.22000.3019
microsoft
windows 11 22h2
≤ 10.0.22621.3737
microsoft
windows 11 23h2
≤ 10.0.22631.3737
microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
+4 more product configuration(s) — see NVD for full list

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

SI-10 requires validation of inputs used to construct resource names, directly stopping malformed or dangerous names from being accepted.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and sanitization to restrict resource names derived from untrusted data.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect improper filename handling but does not itself prevent the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and safe resource naming practices that directly prevent CWE-641.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for handling untrusted input when constructing file or resource names.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles discourage unsafe resource naming but do not prescribe specific controls.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require validation and sanitization of filenames derived from external input.

References