Threats / Microsoft / CVE-2023-29360
CVE-2023-29360
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Streaming Service vulnerability
Microsoft Streaming Service contains an untrusted pointer dereference vulnerability allowing local privilege escalation to SYSTEM level.
Verdict
Today item — known-exploited.
A local attacker can exploit an untrusted pointer dereference in Microsoft Streaming Service to escalate privileges and gain SYSTEM-level access. The vulnerability is actively exploited in the wild.
CISA KEV Yes · 2024-02-295EPSS 0.22133 (verify live)6Exploit Public PoC7CVSS 8.43CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-02-29).
Probability (EPSS)
EPSS 0.22133 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.4 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C) · Affected: Microsoft, Streaming Service. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-822 Untrusted Pointer Dereference — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 261 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I execute code with limited user privileges on a system running Microsoft Streaming Service.
Business
An attacker gains a foothold on an endpoint with standard user access.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger the untrusted pointer dereference by sending a crafted input to the Streaming Service process.
Business
The vulnerability is activated through normal or malformed service interaction.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the pointer dereference to execute arbitrary code in the context of the Streaming Service process.
Business
Code execution occurs within a privileged service boundary.
4
Data at risk — exfiltration narrative 4
Attacker
I escalate my privileges from user-level to SYSTEM level through the compromised service.
Business
The attacker obtains full system control, bypassing access controls.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05