LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38045: Windows TCP/IP Remote Code Execution Vulnerability

Windows TCP/IP Remote Code Execution Vulnerability

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Windows TCP/IP could allow an unauthenticated remote attacker to run code on a vulnerable system. Successful exploitation is rated difficult, but the potential impact includes full compromise of confidentiality, integrity, and availability. Servers and exposed Windows devices warrant prompt attention.

Executive priority

Treat this as a high-priority patching issue, especially for internet-facing and critical Windows servers. There is no supplied evidence of active exploitation, so emergency incident response is not justified solely by this bundle. Nevertheless, unauthenticated network reachability and potential full-system impact support an expedited remediation cycle.

Technical view

CVE-2024-38045 is a network-reachable Windows TCP/IP remote-code-execution vulnerability classified as CWE-122. Its CVSS 3.1 score is 8.1: no privileges or user interaction are required, although attack complexity is high. Successful exploitation could severely affect confidentiality, integrity, and availability.

Likely exposure

Exposure includes the listed Windows 10, Windows 11, Windows Server 2019, and Windows Server 2022 releases. Network-accessible servers and endpoints are the primary concern. The bundle does not specify vulnerable configurations, listening services, or whether perimeter filtering removes exposure.

Exploitation context

The supplied bundle does not establish active exploitation, and KEV is false. CVSS records exploit maturity as unproven and attack complexity as high. These factors reduce immediate likelihood but do not eliminate risk because exploitation requires neither authentication nor user interaction.

Researcher notes

The evidence identifies TCP/IP, remote code execution, and CWE-122 but provides no root-cause detail, triggering packet conditions, affected configuration prerequisites, or public exploit evidence. Validate exposure and remediation against Microsoft’s advisory. Do not infer that every listed installation is equally reachable or exploitable.

Mitigation direction

  • Apply the Microsoft security update identified in the vendor advisory.
  • Prioritize network-exposed servers and business-critical Windows systems.
  • Review Microsoft guidance for any prerequisites, mitigations, or superseding updates.
  • Use network segmentation and access controls to reduce unnecessary reachability.
  • Accelerate patching where compensating controls cannot reliably limit exposure.

Validation and detection

  • Inventory systems running the Windows releases listed in the source bundle.
  • Confirm Microsoft’s applicable security update is installed on each affected asset.
  • Verify update status through endpoint management and vulnerability scanning records.
  • Retest exposed systems after patching and investigate inconsistent scan results.
  • Confirm unsupported or unmanageable systems have documented compensating controls.
Prepared
Confidence
high
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-122: 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-38045 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
1ADP 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-38045Attack 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 180910.0.17763.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 11 Version 24H210.0.26100.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-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.