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 3 Oct 2023.
Windows 10 1809Operating system · Microsoft

CVE-2023-36802

HIGH · 7.8 CVSS v3.1 Published 2023-09-12
Fix available
A fix is available. Upgrade to 10.0.17763.4851 / 10.0.19044.3448 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click 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
Microsoft Streaming Service Proxy Elevation of Privilege 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

CVE-2023-36802 is a local privilege escalation vulnerability in the Microsoft Streaming Service Proxy component of Windows. An authenticated attacker could exploit this vulnerability to gain elevated system privileges on affected Windows systems.

MitigationApply the Microsoft security update for CVE-2023-36802 to all affected Windows systems, or follow Microsoft guidance for mitigating the Streaming Service Proxy attack surface.

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 1809Operating system
Affected:< 10.0.17763.4851
Windows 10 21h2Operating system
Affected:< 10.0.19044.3448
Windows 10 22h2Operating system
Affected:< 10.0.19045.3448
Windows 11 21h2Operating system
Affected:< 10.0.22000.2416
Windows 11 22h2Operating system
Affected:< 10.0.22621.2275
Windows Server 2019Operating system
Affected:< 10.0.17763.4851
Windows Server 2022Operating system
Affected:< 10.0.20348.1970

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify Windows version and build number
    Open Command Prompt or PowerShell and run `winver` to see the OS version and build, or run `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
    Affected if The build number falls below any of these thresholds: 17763.4851, 19044.3448, 19045.3448, 22000.2416, 22621.2275, 20348.1970 depending on your Windows release
  2. Confirm the specific Windows release
    Run `winver` or check System Properties to determine if you are on Windows 10 1809, 10 21h2, 10 22h2, Windows 11 21h2, 11 22h2, Server 2019, or Server 2022
    Affected if You are running one of the affected releases listed in the CVE and your build is below the corresponding threshold for that release
  3. Check if Microsoft Streaming Service Proxy exists
    Run `Get-Service -Name msstreaming` in PowerShell, or check the Windows Services list for a service named "Microsoft Streaming Service Proxy"
    Affected if The service exists on the system (vulnerability only applies if this service is present)
  4. Verify service status and startup configuration
    Run `Get-Service -Name msstreaming | Select-Object Name, Status, StartType` in PowerShell to check if the service is running or set to auto-start
    Affected if The service is installed and running or set to start automatically (the vulnerability can be exploited when the service is active)
  5. Confirm full build number for precise version matching
    Run `ver` in Command Prompt or `[System.Environment]::OSVersion.Version` in PowerShell to get the exact build number (e.g., 10.0.19045.3448)
    Affected if The full build version string is lower than the affected threshold for your specific Windows release

You are affected if your Windows version matches one of the affected releases AND your build number is below the corresponding threshold AND the Microsoft Streaming Service Proxy service is present on the system.

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.17763.4851 / 10.0.19044.3448 / 10.0.19045.3448 or later
Fixed in 10.0.17763.485110.0.19044.344810.0.19045.3448
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2023-36802 to all affected Windows systems, or follow Microsoft guidance for mitigating the Streaming Service Proxy attack surface.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.4851 | Windows 10 21h2: 10.0.19044.3448 | Windows 10 22h2: 10.0.19045.3448 | Windows 11 21h2: 10.0.22000.2416 | Windows 11 22h2: 10.0.22621.2275 | Windows Server 2019: 10.0.17763.4851 | Windows Server 2022: 10.0.20348.1970

  1. Open Settings on the Windows machine
  2. Navigate to Windows Update (Update & Security > Windows Update)
  3. Click 'Check for updates' to download and install the latest security updates
  4. Restart the computer when prompted to complete the installation
  5. Verify the installed version matches or exceeds the fixed version (e.g., run 'winver' to check the OS build number)
Caveat Standard security patch with no expected breaking changes; may require restart

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

Fix this in Windows 10 1809 Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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