What is CVE-2024-38217?

CVE-2024-38217 is Microsoft Windows Mark of the Web (MOTW) Protection Mechanism Failure Vulnerability. The supplied enrichment data classifies it as Unclassified mapped to CWE-693 CWE-693.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2024-38217. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2024-38217 using CVSS 5.4, EPSS 10%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVmedium

CVE-2024-38217

CVE-2024-38217 — Microsoft Windows Mark of the Web (MOTW) Protection Mechanism Failure Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2024-38217 in CISA KEV with required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Windows Mark of the Web Security Feature Bypass Vulnerability

Published Sep 10, 2024Updated Jun 17, 2026Sources: NVD, CISA, FIRST EPSS

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Sep 10, 2024

EPSS

10%

ahead of 95% of scored CVEs

Affects

microsoft

24 products listed

CVSS base

5.4

medium

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade windows_10_version_1507 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Federal deadline Oct 1, 2024 — passed 717 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
microsoft	windows_10_version_1507	—	Vulnerable
microsoft	windows_10_version_1607	—	Vulnerable
microsoft	windows_10_version_1809	—	Vulnerable
microsoft	windows_10_version_21h2	—	Vulnerable
microsoft	windows_10_version_22h2	—	Vulnerable
microsoft	windows_11_version_21h2	—	Vulnerable
microsoft	windows_11_version_22h2	—	Vulnerable
microsoft	windows_11_version_22h3	—	Vulnerable
microsoft	windows_11_version_23h2	—	Vulnerable
microsoft	windows_11_version_24h2	—	Vulnerable
microsoft	windows_server_2008_service_pack_2	—	Vulnerable
microsoft	windows_server_2008_r2_service_pack_1	—	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

None

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
5.4	CVSS 3.1	medium	2.8	2.5	Microsoft (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Weakness & attack patterns

CWE-693

Inferred from the weakness class — not observed against this CVE.

T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness
T1083File and Directory Discovery
T1574.005Hijack Execution Flow: Executable Installer File Permissions Weakness

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Sep 10, 2024

Federal deadline

Oct 1, 2024

passed 717 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable windows_10_version_1507, windows_10_version_1607, windows_10_version_1809, windows_10_version_21h2, windows_10_version_22h2, windows_11_version_21h2, windows_11_version_22h2, windows_11_version_22h3, windows_11_version_23h2, windows_11_version_24h2, windows_server_2008_service_pack_2, windows_server_2008_r2_service_pack_1, windows_server_2008_r2_service_pack_1_server_core_installation, windows_server_2008_service_pack_2_server_core_installation, windows_server_2012, windows_server_2012_server_core_installation, windows_server_2012_r2, windows_server_2012_r2_server_core_installation, windows_server_2016, windows_server_2016_server_core_installation, windows_server_2019, windows_server_2019_server_core_installation, windows_server_2022, windows_server_2022_23h2_edition_server_core_installation.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 5.4 (AV:N)
Jun 17, 2026 · NVD
2024
Added to CISA KEV catalog
Sep 10, 2024 · CISA
Initial · CVE published
Sep 10, 2024 · NVD

References

4 on the record

msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38217
Patch, Vendor Advisory
www.elastic.co/security-labs/dismantling-smart-app-control
Exploit, Third Party Advisory
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-38217
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2024-38217
Vendor Advisory

Elsewhere on this site

microsoftevery CVE for this vendor
September 2024what else CISA listed
Unclassifiedsame class
CWE-693other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2024-38217 is Microsoft Windows Mark of the Web (MOTW) Protection Mechanism Failure Vulnerability, a medium vulnerability affecting windows_10_version_1507, windows_10_version_1607, windows_10_version_1809, windows_10_version_21h2, windows_10_version_22h2, windows_11_version_21h2, windows_11_version_22h2, windows_11_version_22h3, windows_11_version_23h2, windows_11_version_24h2, windows_server_2008_service_pack_2, windows_server_2008_r2_service_pack_1, windows_server_2008_r2_service_pack_1_server_core_installation, windows_server_2008_service_pack_2_server_core_installation, windows_server_2012, windows_server_2012_server_core_installation, windows_server_2012_r2, windows_server_2012_r2_server_core_installation, windows_server_2016, windows_server_2016_server_core_installation, windows_server_2019, windows_server_2019_server_core_installation, windows_server_2022, windows_server_2022_23h2_edition_server_core_installation from microsoft. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2024-38217. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 5.4 describes technical severity, while EPSS 10% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.