Skip to content
Server Security Center
KEVhigh7.8

CVE-2023-36802: Microsoft Streaming Service Proxy Privilege Escalation

Microsoft Streaming Service Proxy · listed in the CISA catalog of actively exploited vulnerabilities since 2023-09-12.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
28%
higher than 98.1% of all CVEs
Added to CISA KEV
2023-09-12
US federal due date 2023-10-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2023-36802 explained

CVE-2023-36802 is a privilege escalation vulnerability in Microsoft Streaming Service Proxy on Windows, classified as a use-after-free weakness (CWE-416). It affects Windows 10 Version 1809, 21H2 and 22H2, Windows 11 version 21H2 and 22H2, and Windows Server 2019 and 2022. CISA lists it as known to be exploited by attackers.

Impact

An attacker who can already run code locally with low privileges can escalate privileges without any user interaction. Successful exploitation has high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so exploitation requires manual steps per target. Attackers are known to use this vulnerability; whether it is used in ransomware campaigns is unknown.

Who is affected

Affected builds: Windows 10 Version 1809, Windows Server 2019 and Server 2019 (Server Core installation) before 10.0.17763.4851; Windows Server 2022 before 10.0.20348.1970; Windows 11 version 21H2 before 10.0.22000.2416; Windows 10 Version 21H2 before 10.0.19044.3448; Windows 11 version 22H2 before 10.0.22621.2283; Windows 10 Version 22H2 before 10.0.19045.3448. The fixed builds are those exact versions: 10.0.17763.4851, 10.0.20348.1970, 10.0.22000.2416, 10.0.19044.3448, 10.0.22621.2283 and 10.0.19045.3448.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Streaming Service Proxy contains an unspecified vulnerability that allows for privilege escalation.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.4851
    Fixed in
    • 10.0.17763.4851
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.4851
    Fixed in
    • 10.0.17763.4851
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.4851
    Fixed in
    • 10.0.17763.4851
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.1970
    Fixed in
    • 10.0.20348.1970
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.2416
    Fixed in
    • 10.0.22000.2416
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.3448
    Fixed in
    • 10.0.19044.3448
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.2283
    Fixed in
    • 10.0.22621.2283
  • Microsoft Windows 10 Version 22H2x64, ARM64, 32-bit
    Affected
    • < 10.0.19045.3448
    Fixed in
    • 10.0.19045.3448

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.4851
    • Microsoft Windows Server 2019: 10.0.17763.4851
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.4851
    • Microsoft Windows Server 2022: 10.0.20348.1970
    • Microsoft Windows 11 version 21H2: 10.0.22000.2416
    • Microsoft Windows 10 Version 21H2: 10.0.19044.3448
    Fixed versions for 2 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36802
  • CISA's deadline for US federal agencies: 2023-10-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to at least the fixed build listed for its Windows version.
  2. Prioritize patching, since CISA lists this vulnerability as known exploited; US federal agencies had a due date of 2023-10-03.
  3. Verify installed build numbers across all Windows 10, Windows 11 and Windows Server 2019/2022 systems after patching.
  4. Limit local logon and low-privileged account access on systems that cannot be patched promptly.
  5. Review systems for signs of compromise, such as unexpected privileged accounts or processes.
  6. Follow the Microsoft advisory for any additional guidance.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

Questions about CVE-2023-36802

Can this be exploited remotely?
No. The attack vector is local. An attacker needs low-privileged access to the system first, but no user interaction is required.
Is CVE-2023-36802 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-09-12. Whether it has been used in ransomware campaigns is unknown.
Which update fixes it?
The Microsoft update that raises the OS build to the fixed version for your release, for example 10.0.19045.3448 for Windows 10 Version 22H2 or 10.0.20348.1970 for Windows Server 2022.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.