cve.bz

CVE-2023-36589 microsoft: Code Injection

7.3 highEPSS 0.8%Fix available

High (7.3) in microsoft. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-02-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-36589 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-36589?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-36589?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-36589 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.4974
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.4974
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.4974
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.4974
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.2031
Microsoft Windows 11 version 21H2from 10.0.0 before 10.0.22000.2538
Microsoft Windows 10 Version 21H2from 10.0.19043.0 before 10.0.19041.3570
Microsoft Windows 11 version 22H2from 10.0.22621.0 before 10.0.22621.2428
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.3570
Microsoft Windows 10 Version 1507from 10.0.10240.0 before 10.0.10240.20232
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.6351
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.6351
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.6351
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.22317
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)from 6.0.6003.0 before 6.0.6003.22317
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.22317
Microsoft Windows Server 2008 R2 Service Pack 1from 6.1.7601.0 before 6.1.7601.26769
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.1.7601.0 before 6.1.7601.26769
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.24523
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.24523
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.21620
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.21620

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON