CVE-2024-21409: .NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 84.8% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: dotnet6-build (Alpine:v3.19) 6.0.129-r0; dotnet6-runtime (Alpine:v3.19) 6.0.29-r0; dotnet7-build (Alpine:v3.19) 7.0.118-r0.
Low priority for now. Upgrade to dotnet6-build (Alpine:v3.19) 6.0.129-r0; dotnet6-runtime (Alpine:v3.19) 6.0.29-r0; dotnet7-build (Alpine:v3.19) 7.0.118-r0 or later.
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
- Published
- Apr 9, 2024
- Updated
- Jun 17, 2026
- EPSS
- 2.5% · 84th percentile
- CWE
- CWE-416
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 7.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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 | .net framework | cpe:2.3:a:microsoft:.net_framework |
| 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 2022 | cpe:2.3:o:microsoft:windows_server_2022 |
| microsoft | .net | cpe:2.3:a:microsoft:.net |
| microsoft | powershell | cpe:2.3:a:microsoft:powershell |
| microsoft | visual studio 2022 | cpe:2.3:a:microsoft:visual_studio_2022 |
| microsoft | windows 10 1607 | cpe:2.3:o:microsoft:windows_10_1607 |
| microsoft | windows 10 1809 | cpe:2.3:o:microsoft:windows_10_1809 |
and 4 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft .net6.0.0 and later · before 6.0.29
- microsoft .net7.0.0 and later · before 7.0.18
- microsoft .net8.0.0 and later · before 8.0.4
- microsoft .net framework3.5
- microsoft .net framework4.6.2
- microsoft .net framework4.7
- microsoft .net framework4.7.1
- microsoft .net framework4.7.2
- microsoft .net framework4.8
- microsoft .net framework4.8.1
- microsoft powershell7.3 and later · before 7.3.12
- microsoft powershell7.2 and later · before 7.2.19
- microsoft powershell7.4 and later · before 7.4.2
- microsoft visual studio 202217.8.0 and later · before 17.8.9
- microsoft visual studio 202217.4.0 and later · before 17.4.18
- microsoft visual studio 202217.9.0 and later · before 17.9.6
- microsoft visual studio 202217.6.0 and later · before 17.6.14
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 .NET 6.0
- 6.0.0 and later · before 6.0.29affected
Microsoft .NET 7.0
- 7.0.0 and later · before 7.0.18affected
Microsoft .NET 8.0
- 8.0 and later · before 8.0.4affected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2
- 4.7.0 and later · before 4.7.4092.0affected
Microsoft Microsoft .NET Framework 3.5 AND 4.8
- 4.8.0 and later · before 4.8.4718.0affected
Microsoft Microsoft .NET Framework 3.5 AND 4.8.1
- 4.8.1 and later · before 4.8.9236.0affected
Microsoft Microsoft .NET Framework 4.6.2
- 4.7.0 and later · before 4.7.4092.0affected
Microsoft Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2
- 4.7.0 and later · before 4.7.4092.0affected
Microsoft Microsoft .NET Framework 4.8
- 4.8.0 and later · before 4.8.4718.0affected
Microsoft Microsoft Visual Studio 2022 version 17.4
- 17.4.0 and later · before 17.4.18affected
Microsoft Microsoft Visual Studio 2022 version 17.6
- 17.6.0 and later · before 17.6.14affected
Microsoft Microsoft Visual Studio 2022 version 17.8
- 17.8.0 and later · before 17.8.9affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.19 | dotnet6-build | before 6.0.129-r0 | 6.0.129-r0 |
| Alpine:v3.19 | dotnet6-runtime | before 6.0.29-r0 | 6.0.29-r0 |
| Alpine:v3.19 | dotnet7-build | before 7.0.118-r0 | 7.0.118-r0 |
| Alpine:v3.19 | dotnet7-runtime | before 7.0.18-r0 | 7.0.18-r0 |
| Alpine:v3.20 | dotnet8-runtime | before 8.0.4-r0 | 8.0.4-r0 |
| NuGet | Microsoft.WindowsDesktop.App.Runtime.win-arm64 | from 7.0.0 · before 7.0.18 | 7.0.18 |
| NuGet | Microsoft.WindowsDesktop.App.Runtime.win-arm64 | from 8.0.0 · before 8.0.4 | 8.0.4 |
| NuGet | Microsoft.WindowsDesktop.App.Runtime.win-arm64 | before 6.0.29 | 6.0.29 |
| NuGet | Microsoft.WindowsDesktop.App.Runtime.win-x64 | from 7.0.0 · before 7.0.18 | 7.0.18 |
| NuGet | Microsoft.WindowsDesktop.App.Runtime.win-x64 | from 8.0.0 · before 8.0.4 | 8.0.4 |
| NuGet | Microsoft.WindowsDesktop.App.Runtime.win-x64 | before 6.0.29 | 6.0.29 |
| NuGet | Microsoft.WindowsDesktop.App.Runtime.win-x86 | from 7.0.0 · before 7.0.18 | 7.0.18 |
| NuGet | Microsoft.WindowsDesktop.App.Runtime.win-x86 | from 8.0.0 · before 8.0.4 | 8.0.4 |
| NuGet | Microsoft.WindowsDesktop.App.Runtime.win-x86 | before 6.0.29 | 6.0.29 |
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-0646A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote KEV99Now
- CVE-2024-29059.NET Framework Information Disclosure VulnerabilityKEV90Now
- CVE-2017-8759Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to execute code remotely via a malicious documeKEV88Now
Published before and after this one in the same product
- ← EarlierCVE-2023-36049Nov 14, 2023 · .NET, .NET Framework, and Visual Studio Elevation of Privilege Vulnerability41Plan
- ← EarlierCVE-2024-21312Jan 9, 2024 · .NET Framework Denial of Service Vulnerability31Monitor
- Later →CVE-2024-38081Jul 9, 2024 · .NET, .NET Framework, and Visual Studio Elevation of Privilege Vulnerability29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:dotnet6-build | 6.0.129-r0 · Alpine:v3.19 | Package registry (OSV) |
| alpine:dotnet6-runtime | 6.0.29-r0 · Alpine:v3.19 | Package registry (OSV) |
| alpine:dotnet7-build | 7.0.118-r0 · Alpine:v3.19 | Package registry (OSV) |
| alpine:dotnet7-runtime | 7.0.18-r0 · Alpine:v3.19 | Package registry (OSV) |
| alpine:dotnet8-runtime | 8.0.4-r0 · Alpine:v3.20 | Package registry (OSV) |
| NuGet:Microsoft.WindowsDesktop.App.Runtime.win-arm64 | 6.0.29 | Package registry (OSV) |
| NuGet:Microsoft.WindowsDesktop.App.Runtime.win-arm64 | 7.0.18 | Package registry (OSV) |
| NuGet:Microsoft.WindowsDesktop.App.Runtime.win-arm64 | 8.0.4 | Package registry (OSV) |
| NuGet:Microsoft.WindowsDesktop.App.Runtime.win-x64 | 6.0.29 | Package registry (OSV) |
| NuGet:Microsoft.WindowsDesktop.App.Runtime.win-x64 | 7.0.18 | Package registry (OSV) |
| NuGet:Microsoft.WindowsDesktop.App.Runtime.win-x64 | 8.0.4 | Package registry (OSV) |
| NuGet:Microsoft.WindowsDesktop.App.Runtime.win-x86 | 6.0.29 | Package registry (OSV) |
| NuGet:Microsoft.WindowsDesktop.App.Runtime.win-x86 | 7.0.18 | Package registry (OSV) |
| NuGet:Microsoft.WindowsDesktop.App.Runtime.win-x86 | 8.0.4 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2025-02-12 |
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.
- Published
- First PoC+308 d
- TodayNov 7, 2026+942 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.