LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38119: Windows Network Address Translation (NAT) Remote Code Execution Vulnerability

Windows Network Address Translation (NAT) Remote Code Execution Vulnerability

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Windows Network Address Translation could let an unauthenticated attacker on an adjacent network execute code. Successful exploitation is considered difficult, but compromise could affect confidentiality, integrity, and availability. The supplied evidence does not establish internet-scale reachability or active exploitation.

Executive priority

Treat this as a high-priority patching and exposure-review item, especially for Windows servers or endpoints involved in NAT. It warrants timely remediation, but the supplied evidence does not justify an emergency response based on active exploitation.

Technical view

CVE-2024-38119 is a CWE-416 use-after-free vulnerability in Windows NAT. Its CVSS 3.1 score is 7.5, with adjacent-network access, high attack complexity, no privileges, and no user interaction. Successful exploitation may enable remote code execution with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure applies to the listed Windows 10, Windows 11, and Windows Server releases. Risk is most relevant where the vulnerable NAT functionality is present and reachable from an adjacent network. The bundle does not identify affected configurations, ports, services, or internet exposure conditions.

Exploitation context

The CVSS vector indicates exploitation requires adjacent-network access and high complexity, but neither credentials nor user interaction. The supplied record is not marked as CISA KEV, and no cited evidence establishes active exploitation or a public exploit. Absence from KEV does not prove exploitation is impossible.

Researcher notes

Key constraints are AV:A and AC:H; testing should focus on authorized adjacent-network scenarios without assuming direct internet exploitability. The record identifies CWE-416 but supplies no root-cause details, affected component paths, indicators, KB identifiers, proof of concept, or confirmed exploitation telemetry.

Mitigation direction

  • Review Microsoft’s CVE advisory and install the applicable security update for each affected Windows release.
  • Prioritize affected systems performing NAT or reachable from less-trusted adjacent networks.
  • Use network segmentation to reduce untrusted adjacent access while updates are pending.
  • Check Microsoft guidance for product-specific mitigations or prerequisites not included in the source bundle.

Validation and detection

  • Inventory Windows editions, versions, and builds against the affected-product list.
  • Determine which affected hosts provide or use Windows NAT functionality.
  • Verify applicable Microsoft security updates are installed using the vendor advisory.
  • Confirm adjacent-network controls restrict access from untrusted segments.
  • Monitor vendor guidance for revised affected-version or remediation details.
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-416: 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-38119 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
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/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
7.5CVSS 3.1HighCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.65.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:A/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 150710.0.10240.0Listed
MicrosoftWindows 10 Version 160710.0.14393.0Listed
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 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-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.