CVE-2023-29360
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 · uneditedMicrosoft Streaming Service 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 confidenceMicrosoft Streaming Service contains an elevation of privilege vulnerability that could allow an authenticated attacker to gain higher-level system privileges. The CVSS 8.4 score indicates significant impact requiring authenticated access.
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< 10.0.14393.5989< 10.0.17763.4499< 10.0.19044.3086< 10.0.19045.3086< 10.0.22000.2057< 10.0.22621.1848< 10.0.14393.5989< 10.0.17763.4499CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows versionOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build number.Affected if The Windows version and build number fall within any of these vulnerable ranges: Windows 10 1607 < 10.0.14393.5989, Windows 10 1809 < 10.0.17763.4499, Windows 10 21h2 < 10.0.19044.3086, Windows 10 22h2 < 10.0.19045.3086, Windows 11 21h2 < 10.0.22000.2057, Windows 11 22h2 < 10.0.22621.1848, Windows S
-
Identify Microsoft Streaming ServiceOpen PowerShell and run 'Get-Service -Name MSStreamSvc -ErrorAction SilentlyContinue' or query the service via 'sc query MSStreamSvc' in Command Prompt.Affected if The Microsoft Streaming Service (MSStreamSvc) exists on the system, indicating the vulnerable component is present.
-
Check service status and startup typeRun 'Get-Service -Name MSStreamSvc | Select-Object Name, Status, StartType' in PowerShell or 'sc qc MSStreamSvc' in Command Prompt to check if the service is running and its configuration.Affected if The MSStreamSvc service is in a running state (Status equals 'Running'), making the vulnerability exploitable.
A system is affected if it runs a Windows version within the affected build ranges AND the Microsoft Streaming Service (MSStreamSvc) is installed and running.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.598910.0.17763.449910.0.19044.3086
Apply Microsoft security updates for CVE-2023-29360 via Windows Update or enterprise patch management systems. Verify Microsoft Streaming Service functionality after patching.
Apply the Microsoft security update KB5031445 or subsequent relevant patches for CVE-2023-29360 (specific KB varies by Windows version)
- Check current Windows version by running `winver` or `systeminfo` in Command Prompt
- Identify the specific Windows build number from the affected versions list for your system
- Apply the appropriate Microsoft security update for CVE-2023-29360 via Windows Update (Settings > Update & Security > Windows Update > Check for updates)
- Alternatively, manually download the security update from the Microsoft Update Catalog using the KB number corresponding to your Windows version
- Restart the system after applying the update
- Verify the installed build matches or exceeds the fixed version: Windows 10 1607 should be 10.0.14393.5989 or later; Windows 10 1809 should be 10.0.17763.4499 or later; Windows 10 21h2 should be 10.0.19044.3086 or later; Windows 10 22h2 should be 10.0.19045.3086 or later; Windows 11 21h2 should be 10.0.22000.2057 or later; Windows 11 22h2 should be 10.0.22621.1848 or later; Windows Server 2016 sho
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-29360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29360 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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