dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-30050

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 10.0.10240.20651 / 10.0.14393.6981 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows Mark of the Web Security Feature Bypass Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This vulnerability allows bypassing the Windows Mark of the Web (MOTW) security feature, which normally applies protective restrictions to files downloaded from the internet or originating from untrusted sources. By circumventing MOTW, potentially malicious files could execute without the typical security warnings or restrictions that users expect, leading to increased risk of code execution attacks.

MitigationApply the Microsoft security update for CVE-2024-30050 to all affected Windows systems. Verify that the Mark of the Web functionality is functioning correctly after patching by testing with sample downloaded files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20651
Windows 10 1607Operating system
Affected:< 10.0.14393.6981
Windows 10 1809Operating system
Affected:< 10.0.17763.5820
Windows 10 21h2Operating system
Affected:< 10.0.19044.4412
Windows 10 22h2Operating system
Affected:< 10.0.19045.4412
Windows 11 21h2Operating system
Affected:< 10.0.22000.2960
Windows 11 22h2Operating system
Affected:< 10.0.22621.3593
Windows 11 23h2Operating system
Affected:< 10.0.22631.3593

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the Windows build number
    Affected if The displayed build number is lower than the fixed version for your Windows release (10.0.10240.20651 for 1507, 10.0.14393.6981 for 1607, 10.0.17763.5820 for 1809, 10.0.19044.4412 for 21h2, 10.0.19045.4412 for 22h2, 10.0.22000.2960 for Win11 21h2, 10.0.22621.3593 for Win11 22h2, or 10.0.22631.3593 f
  2. Confirm Windows edition
    Run 'winver' or check System Properties to identify whether you are running Windows 10 1507, 1607, 1809, 21h2, 22h2 or Windows 11 21h2, 22h2, or 23h2
    Affected if The installed Windows edition matches one of the affected versions listed and the build number is below the corresponding fixed build
  3. Verify if the security update is installed
    Open Settings > Windows Update > Update history and look for a security update installed around the date of CVE-2024-30050 patch release, or check the installed updates via 'wmic qfe list' in Command Prompt
    Affected if The security update for CVE-2024-30050 is not listed in installed updates and the Windows version remains below the fixed build threshold

A system is affected if it runs one of the specified Windows 10 or Windows 11 versions AND has a build number lower than the fixed threshold for that release, indicating the CVE-2024-30050 patch has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20651 / 10.0.14393.6981 / 10.0.17763.5820 or later
Fixed in 10.0.10240.2065110.0.14393.698110.0.17763.5820
Interim mitigation

Apply the Microsoft security update for CVE-2024-30050 to all affected Windows systems. Verify that the Mark of the Web functionality is functioning correctly after patching by testing with sample downloaded files.

Recommended fix High confidence

Windows 10 1507: build 10.0.10240.20651 | Windows 10 1607: build 10.0.14393.6981 | Windows 10 1809: build 10.0.17763.5820 | Windows 10 21h2: build 10.0.19044.4412 | Windows 10 22h2: build 10.0.19045.4412 | Windows 11 21h2: build 10.0.22000.2960 | Windows 11 22h2: build 10.0.22621.3593 | Windows 11 2

  1. Open Windows Settings
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Alternatively, download the specific security update for your Windows version from the Microsoft Update Catalog
Caveat Standard Windows update risks apply (potential for temporary compatibility issues; backup recommended for enterprise deployments)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30050 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30050 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data