Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker could exploit Microsoft Message Queuing on affected Windows systems to run code, potentially taking control of data and services. The 9.8 CVSS score reflects low attack complexity, no required privileges, and no user interaction. Business impact could include system compromise, data loss, and operational disruption.
Executive priority
Treat as an urgent patching priority because compromise requires neither credentials nor user interaction and could produce complete system impact. Accelerate remediation for reachable or critical MSMQ hosts. Where patching cannot occur promptly, require documented network isolation and service-necessity review.
Technical view
CVE-2023-36911 is an MSMQ remote-code-execution vulnerability associated with integer overflow (CWE-190). Its CVSS 3.1 vector indicates network reachability, low complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impacts. Microsoft identifies affected Windows client and server releases and provides a security update.
Likely exposure
Potential exposure includes listed Windows 10 and 11 releases and Windows Server 2008 through 2019 systems using MSMQ. The bundle does not establish whether MSMQ is enabled by default or which ports are reachable. Prioritize internet-facing, externally reachable, and business-critical MSMQ systems for verification.
Exploitation context
The supplied CVSS data indicates unauthenticated network exploitation with low complexity and no user action. The source bundle marks the CVE as absent from KEV and provides no evidence of active exploitation. That absence should not be treated as proof that exploitation is impossible or has never occurred.
Researcher notes
The strongest supported details are the 9.8 CVSS vector, CWE-190 classification, affected Windows versions, and Microsoft patch reference. The bundle does not describe the vulnerable message-processing path, affected MSMQ configurations, indicators of compromise, exact update identifiers, or observed attacks. Consult the Microsoft advisory for release-specific update information.
Mitigation direction
- Apply the Microsoft security update applicable to each affected Windows release.
- Follow Microsoft guidance for unsupported or extended-support Windows versions.
- Restrict untrusted network access to MSMQ services while remediation is pending.
- Disable MSMQ where confirmed unnecessary, following change-control and dependency review.
Validation and detection
- Inventory systems running the Windows releases identified in the source bundle.
- Determine where MSMQ is installed, enabled, and reachable from untrusted networks.
- Verify each affected system has the corresponding Microsoft security update installed.
- Confirm network controls restrict MSMQ access to documented trusted sources.
- Review security telemetry for suspicious activity involving exposed MSMQ services.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-36911 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C3.95.9microsoftVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft Message Queuing (MSMQ) Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.