dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 7 Dec 2023.
Windows 10 1507Operating system · Microsoft

CVE-2023-36584

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to 10.0.10240.20232 / 10.0.17763.4974 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Patch available

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 is a Windows security feature bypass vulnerability affecting the Mark of the Web (MOTW) mechanism. MOTW is a Windows security feature that tags files downloaded from the internet with identifying metadata, allowing Windows to apply appropriate security restrictions such as prompting users or blocking potentially dangerous file types. This vulnerability allows attackers to potentially circumvent these MOTW protections.

MitigationApply Microsoft security updates for CVE-2023-36584 when available through Windows Update or the Microsoft Security Update Guide.

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.20232
Windows 10 1809Operating system
Affected:< 10.0.17763.4974
Windows 10 21h1Operating system
Affected:< 10.0.19041.3570
Windows 10 22h2Operating system
Affected:< 10.0.19041.3570
Windows 11 21h2Operating system
Affected:< 10.0.22000.2538
Windows 11 22h2Operating system
Affected:< 10.0.22621.2428
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2

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 your Windows build version
    Open Command Prompt and run 'winver' to display the Windows version and build number, or run 'systeminfo | findstr /B /C:"OS Version"' for detailed build information
    Affected if The build number is less than the fixed version for your Windows release (10.0.10240.20232 for 1507, 10.0.17763.4974 for 1809, 10.0.19041.3570 for 21h1/22h2, 10.0.22000.2538 for 11 21h2, 10.0.22621.2428 for 11 22h2) or for Server 2008/2012 any version is affected
  2. Verify Mark of the Web is functioning
    Download a file from the internet using a standard browser, then right-click the file, select Properties, and inspect the 'Security' section for a checkbox indicating 'This file came from another computer and might be blocked'
    Affected if The file does not show the MotW warning in Properties, indicating the security marker is not being applied or is being bypassed
  3. Inspect Zone.Identifier metadata
    Open PowerShell and run 'Get-Item -Path 'C:\path\to\downloaded\file.exe' -Stream *' to list all alternate data streams, then check for 'Zone.Identifier' stream content using 'Get-Content -Path 'C:\path\to\downloaded\file.exe' -Stream Zone.Identifier'
    Affected if No Zone.Identifier stream exists or the stream shows ZoneId=0 (Trusted) instead of ZoneId=3 (Internet) for files downloaded from untrusted sources

You are affected if your Windows build is below the fixed version for your specific release AND downloaded files are not properly tagged with MotW Zone.Identifier metadata indicating ZoneId=3 (Internet).

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.20232 / 10.0.17763.4974 / 10.0.19041.3570 or later
Fixed in 10.0.10240.2023210.0.17763.497410.0.19041.3570
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply Microsoft security updates for CVE-2023-36584 when available through Windows Update or the Microsoft Security Update Guide.

Recommended fix High confidence
  1. Identify your current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Microsoft Update Catalog (https://catalog.update.microsoft.com) and search for CVE-2023-36584 or the corresponding monthly security update for your Windows version
  3. Download and install the applicable security update from Microsoft Update
  4. Restart the computer when prompted to complete the installation
  5. Verify the update was installed successfully by checking Windows Update history

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36584 — 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-2023-36584 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