NVD / CVE Program· CNA microsoft

CVE-2024-21339: Windows USB Generic Parent Driver Remote Code Execution Vulnerability

MediumCVSS 6.4 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 25/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.55% (FIRST EPSS).
Physical access to the device is required. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

BDU:2024-01401

Published: Feb 13, 2024
Updated: Aug 10, 2026
EPSS: 0.5% · 46th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 25 / 40 · 6.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · microsoft: 6.4; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
microsoft	windows 10 1809	cpe:2.3:o:microsoft:windows_10_1809
microsoft	windows 10 21h2	cpe:2.3:o:microsoft:windows_10_21h2
microsoft	windows 10 22h2	cpe:2.3:o:microsoft:windows_10_22h2
microsoft	windows 11 21h2	cpe:2.3:o:microsoft:windows_11_21h2
microsoft	windows 11 22h2	cpe:2.3:o:microsoft:windows_11_22h2
microsoft	windows 11 23h2	cpe:2.3:o:microsoft:windows_11_23h2
microsoft	windows server 2019	cpe:2.3:o:microsoft:windows_server_2019
microsoft	windows server 2022	cpe:2.3:o:microsoft:windows_server_2022
microsoft	windows server 2022 23h2	cpe:2.3:o:microsoft:windows_server_2022_23h2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.

Microsoft Windows 10 Version 1809
- 10.0.17763.0 and later · before 10.0.17763.5458affected
- 10.0.0 and later · before 10.0.17763.5458affected
Microsoft Windows 10 Version 21H2
- 10.0.19043.0 and later · before 10.0.19044.4046affected
Microsoft Windows 10 Version 22H2
- 10.0.19045.0 and later · before 10.0.19045.4046affected
Microsoft Windows 11 version 21H2
- 10.0.0 and later · before 10.0.22000.2777affected
Microsoft Windows 11 version 22H2
- 10.0.22621.0 and later · before 10.0.22621.3155affected
Microsoft Windows 11 version 22H3
- 10.0.22631.0 and later · before 10.0.22631.3155affected
Microsoft Windows 11 Version 23H2
- 10.0.22631.0 and later · before 10.0.22631.3155affected
Microsoft Windows Server 2019
- 10.0.17763.0 and later · before 10.0.17763.5458affected
Microsoft Windows Server 2019 (Server Core installation)
- 10.0.17763.0 and later · before 10.0.17763.5458affected
Microsoft Windows Server 2022
- 10.0.20348.0 and later · before 10.0.20348.2322affected
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
- 10.0.25398.0 and later · before 10.0.25398.709affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

microsoft windows server 2019before 10.0.17763.5458
microsoft windows server 2022before 10.0.20348.2322
microsoft windows server 2022 23h2before 10.0.25398.709

Same product

microsoft: all records

Other highest-scoring records for the same primary product.

CVE-2024-21412Internet Shortcut Files Security Feature Bypass VulnerabilityKEV
92Now
CVE-2021-36934Windows Elevation of Privilege VulnerabilityKEV
81Now
CVE-2024-21338Windows Kernel Elevation of Privilege VulnerabilityKEV
80Now

Published before and after this one in the same product

← EarlierCVE-2024-21310Jan 9, 2024 · Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability
34Monitor
← EarlierCVE-2024-21304Feb 13, 2024 · Trusted Compute Base Elevation of Privilege Vulnerability
16Monitor
Later →CVE-2024-21341Feb 13, 2024 · Windows Kernel Remote Code Execution Vulnerability
27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2023-36802154 days apartMicrosoft Streaming Service Proxy Elevation of Privilege VulnerabilityKEV
69This week
CVE-2025-30400455 days apartMicrosoft DWM Core Library Elevation of Privilege VulnerabilityKEV
62This week
CVE-2025-49724511 days apartWindows Connected Devices Platform Service Remote Code Execution Vulnerability
38Monitor
CVE-2024-30089119 days apartMicrosoft Streaming Service Elevation of Privilege Vulnerability
33Monitor
CVE-2023-35382189 days apartWindows Kernel Elevation of Privilege Vulnerability
33Monitor
CVE-2024-43582238 days apartRemote Desktop Protocol Server Remote Code Execution Vulnerability
33Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0110 · Feb 16, 2024(Microsoft Güvenlik Güncellemesi)

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Physical access to the device is required.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Physical
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21339

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records