Microsoft Streaming Service Elevation of Privilege Vulnerability
CVE-2023-29360
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-02-29), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.4 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 22%
- EPSS %ILE
- 98%
- KEV
- ⚠ Exploited
Published
June 14, 2023
Last Modified
October 28, 2025
Advisory Details (2)
Auto-updated Jun 2, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-29360Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-29360Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 99× in last 7d / 416× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,373 total refreshes for this CVE.
- 2026-09-08 11:38 UTCVendor advisory
- 2026-09-08 11:38 UTCGHSA enrichment
- 2026-09-08 07:43 UTCVendor advisory
- 2026-09-08 07:43 UTCGHSA enrichment
- 2026-09-08 03:51 UTCVendor advisory
- 2026-09-08 03:51 UTCGHSA enrichment
- 2026-09-07 23:57 UTCVendor advisory
- 2026-09-07 23:57 UTCGHSA enrichment
- 2026-09-07 20:05 UTCVendor advisory
- 2026-09-07 20:05 UTCGHSA enrichment
- 2026-09-07 16:13 UTCVendor advisory
- 2026-09-07 16:12 UTCGHSA enrichment
- 2026-09-07 12:20 UTCVendor advisory
- 2026-09-07 12:20 UTCGHSA enrichment
- 2026-09-07 08:24 UTCVendor advisory
- 2026-09-07 08:23 UTCGHSA enrichment
- 2026-09-07 04:27 UTCVendor advisory
- 2026-09-07 04:26 UTCGHSA enrichment
- 2026-09-07 00:30 UTCVendor advisory
- 2026-09-07 00:30 UTCGHSA enrichment
- 2026-09-06 20:38 UTCVendor advisory
- 2026-09-06 20:37 UTCGHSA enrichment
- 2026-09-06 16:44 UTCEG score recompute
- 2026-09-06 16:44 UTCVendor advisory
- 2026-09-06 16:44 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 12:51 UTCVendor advisory
- 2026-09-06 12:51 UTCGHSA enrichment
- 2026-09-06 08:58 UTCVendor advisory
- 2026-09-06 08:58 UTCGHSA enrichment
- 2026-09-06 05:06 UTCVendor advisory
- 2026-09-06 05:06 UTCGHSA enrichment
- 2026-09-06 01:12 UTCVendor advisory
- 2026-09-06 01:12 UTCGHSA enrichment
- 2026-09-05 21:18 UTCVendor advisory
- 2026-09-05 21:18 UTCGHSA enrichment
- 2026-09-05 17:26 UTCEG score recompute
- 2026-09-05 17:26 UTCVendor advisory
- 2026-09-05 17:25 UTCGHSA enrichment
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 13:33 UTCVendor advisory
- 2026-09-05 13:32 UTCGHSA enrichment
- 2026-09-05 09:40 UTCVendor advisory
- 2026-09-05 09:40 UTCGHSA enrichment
- 2026-09-05 05:47 UTCVendor advisory
- 2026-09-05 05:47 UTCGHSA enrichment
- 2026-09-05 01:54 UTCVendor advisory
- 2026-09-05 01:54 UTCGHSA enrichment
- 2026-09-04 22:01 UTCVendor advisory
- 2026-09-04 22:01 UTCGHSA enrichment
- 2026-09-04 18:07 UTCVendor advisory
- 2026-09-04 18:07 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 14:13 UTCEG score recompute
- 2026-09-04 14:13 UTCVendor advisory
- 2026-09-04 14:13 UTCGHSA enrichment
- 2026-09-04 13:58 UTCEPSS rescore
- 2026-09-04 10:20 UTCVendor advisory
- 2026-09-04 10:20 UTCGHSA enrichment
- 2026-09-04 06:26 UTCEG score recompute
- 2026-09-04 06:26 UTCVendor advisory
- 2026-09-04 06:25 UTCGHSA enrichment
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-04 02:31 UTCVendor advisory
- 2026-09-04 02:30 UTCGHSA enrichment
- 2026-09-03 22:37 UTCVendor advisory
- 2026-09-03 22:37 UTCGHSA enrichment
- 2026-09-03 18:43 UTCVendor advisory
- 2026-09-03 18:43 UTCGHSA enrichment
- 2026-09-03 14:48 UTCVendor advisory
- 2026-09-03 14:47 UTCGHSA enrichment
- 2026-09-03 10:54 UTCVendor advisory
- 2026-09-03 10:54 UTCGHSA enrichment
- 2026-09-03 07:00 UTCVendor advisory
- 2026-09-03 07:00 UTCGHSA enrichment
- 2026-09-03 03:07 UTCVendor advisory
- 2026-09-03 03:07 UTCGHSA enrichment
- 2026-09-02 23:14 UTCVendor advisory
- 2026-09-02 23:14 UTCGHSA enrichment
- 2026-09-02 19:21 UTCVendor advisory
- 2026-09-02 19:21 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 15:28 UTCEG score recompute
- 2026-09-02 15:28 UTCVendor advisory
- 2026-09-02 15:27 UTCGHSA enrichment
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-02 11:33 UTCVendor advisory
- 2026-09-02 11:33 UTCGHSA enrichment
- 2026-09-02 07:37 UTCVendor advisory
- 2026-09-02 07:37 UTCGHSA enrichment
- 2026-09-02 03:43 UTCVendor advisory
- 2026-09-02 03:42 UTCGHSA enrichment
- 2026-09-01 23:48 UTCVendor advisory
- 2026-09-01 23:48 UTCGHSA enrichment
- 2026-09-01 19:55 UTCVendor advisory
- 2026-09-01 19:55 UTCGHSA enrichment
- 2026-09-01 16:03 UTCEG score recompute
- 2026-09-01 16:03 UTCVendor advisory
- 2026-09-01 16:03 UTCGHSA enrichment
- 2026-09-01 13:51 UTCEPSS rescore
Publicly available exploits
(2 references)Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoC0xDivyanshu-new/CVE-2023-29360First seen Aug 31, 2024
POC for CVE-2023-29360
Open source ↗ - GitHub PoCNero22k/cve-2023-29360First seen Sep 24, 2023
Exploit for CVE-2023-29360 targeting MSKSSRV.SYS driver
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-822
- CVE-2023-1437EG 9.8CRITICAL
- CVE-2018-12548EG 9.8CRITICAL
- CVE-2018-17893EG 9.8EPSS p93CRITICAL
- CVE-2018-14811EG 9.8CRITICAL
- CVE-2018-7497EG 9.8CRITICAL
- CVE-2024-36461EG 9.1CRITICAL
- CVE-2023-21643EG 9.1CRITICAL
- CVE-2024-35250NVD 7.8EG 9.0 KEVEPSS p98CRITICAL
- CVE-2024-21338NVD 7.8EG 9.0 KEVEPSS p99CRITICAL
- CVE-2023-36033NVD 7.8EG 9.0 KEVEPSS p96CRITICAL
Frequently asked(6)
What is CVE-2023-29360?
When was CVE-2023-29360 disclosed?
Is CVE-2023-29360 actively exploited?
What is the CVSS score of CVE-2023-29360?
Which products are affected by CVE-2023-29360?
How do I remediate CVE-2023-29360?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-29360
Is Your Infrastructure Affected by CVE-2023-29360?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.