LiveActive security incident?Get immediate response
CVE Record

CVE-2024-21357: Windows Pragmatic General Multicast (PGM) Remote Code Execution Vulnerability

Windows Pragmatic General Multicast (PGM) Remote Code Execution Vulnerability

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A network attacker could potentially take control of an affected Windows system through its Pragmatic General Multicast functionality. Successful exploitation could compromise sensitive data, alter systems, or cause outages. Exploitation is rated difficult, but requires neither credentials nor user interaction.

Executive priority

Treat as a high-priority patching and exposure-assessment item, especially for reachable servers and sensitive environments. Immediate emergency response is not evidenced because exploitation is unproven and technically complex, but unauthenticated remote code execution warrants timely remediation.

Technical view

CVE-2024-21357 is a Windows PGM remote code execution vulnerability classified as CWE-843, access of a resource using an incompatible type. CVSS 3.1 is 8.1: network-accessible, high complexity, no privileges or user interaction, unchanged scope, and high confidentiality, integrity, and availability impacts.

Likely exposure

Exposure is limited to the affected Windows client and server versions identified by Microsoft, particularly systems where PGM is usable and reachable over a network. The bundle does not establish whether PGM is enabled by default, identify required ports, or provide complete configuration prerequisites.

Exploitation context

The source bundle does not support claims of active exploitation: the CVE is not listed as KEV, and its CVSS exploit-maturity value is unproven. Exploitation requires high complexity, which reduces likelihood but does not remove the risk from reachable, unpatched systems.

Researcher notes

The supplied evidence identifies CWE-843 and the CVSS characteristics but provides no root-cause details, attack preconditions, affected component versions, indicators, or proof-of-concept status. Validate conclusions against the current Microsoft advisory. Do not infer exposure solely from the operating-system version.

Mitigation direction

  • Review Microsoft's CVE advisory and apply the applicable security update.
  • Prioritize network-reachable systems and high-value Windows servers.
  • Restrict unnecessary network access to PGM functionality where operationally safe.
  • Follow Microsoft guidance for unsupported or legacy Windows versions.

Validation and detection

  • Inventory systems running the specifically listed Windows versions.
  • Confirm applicable Microsoft security updates are installed successfully.
  • Identify whether PGM is enabled, used, and network-reachable in each environment.
  • Verify network controls limit unnecessary access to affected systems.
  • Monitor vendor guidance for revised affected-version or remediation information.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-843: 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 lookup
description · low confidence lookup

Execution 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 lookup
cve · low confidence lookup

CVE-2024-21357 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

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.

1CVSS vectors
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.25.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2024-21357Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 150710.0.10240.0Listed
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 180910.0.0Listed
MicrosoftWindows 10 Version 21H210.0.19043.0Listed
MicrosoftWindows 10 Version 22H210.0.19045.0Listed
MicrosoftWindows 11 version 21H210.0.0Listed
MicrosoftWindows 11 version 22H210.0.22621.0Listed
MicrosoftWindows 11 version 22H310.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0Listed
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0Listed
MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)6.0.6003.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-843 · source CWE mapping

Access of Resource Using Incompatible Type ('Type Confusion')

Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.