CVE-2023-36792: Visual Studio Remote Code Execution Vulnerability
Noroxi assessment
Priority: Monitor (action score 31/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: 1.2% (FIRST EPSS); higher than 68.6% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Microsoft.NETCore.App.Runtime.win-arm64 (NuGet) 6.0.22, 7.0.11; Microsoft.NETCore.App.Runtime.win-x64 (NuGet) 6.0.22, 7.0.11; Microsoft.NETCore.App.Runtime.win-x86 (NuGet) 6.0.22, 7.0.11.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Microsoft.NETCore.App.Runtime.win-arm64 (NuGet) 6.0.22, 7.0.11; Microsoft.NETCore.App.Runtime.win-x64 (NuGet) 6.0.22, 7.0.11; Microsoft.NETCore.App.Runtime.win-x86 (NuGet) 6.0.22, 7.0.11 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
- Sep 12, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 68th percentile
- CWE
- CWE-190
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:L/AC:L/PR:N/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
- No public exploit code on record
- 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 server 2008 | cpe:2.3:o:microsoft:windows_server_2008 |
| microsoft | windows server 2012 | cpe:2.3:o:microsoft:windows_server_2012 |
| 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 server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
| microsoft | windows server 2022 | cpe:2.3:o:microsoft:windows_server_2022 |
| microsoft | windows 11 22h2 | cpe:2.3:o:microsoft:windows_11_22h2 |
| microsoft | windows 10 1607 | cpe:2.3:o:microsoft:windows_10_1607 |
| microsoft | windows server 2016 | cpe:2.3:o:microsoft:windows_server_2016 |
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
- microsoft .net7.0.0
- microsoft .net framework2.0
- microsoft .net framework3.0
- microsoft .net framework3.5
- microsoft .net framework3.5.1
- 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 visual studio 201715.0 and later · before 15.9.57
- microsoft visual studio 201916.0 and later · before 16.11.30
- microsoft visual studio 202217.2 and later · before 17.2.19
- microsoft visual studio 202217.4 and later · before 17.4.11
- microsoft visual studio 202217.7 and later · before 17.7.4
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.24affected
Microsoft .NET 7.0
- 7.0.0 and later · before 7.0.13affected
Microsoft Microsoft .NET Framework 2.0 Service Pack 2
- 2.0.0 and later · before 3.0.30729.8957affected
Microsoft Microsoft .NET Framework 3.0 Service Pack 2
- 3.0.0 and later · before 3.0.30729.8957affected
Microsoft Microsoft .NET Framework 3.5
- 3.5.0 and later · before 3.0.30729.8957affected
Microsoft Microsoft .NET Framework 3.5 and 4.6.2
- 4.7.0 and later · before 10.0.10240.20162affected
Microsoft Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2
- 3.0.0.0 and later · before 10.0.14393.6252affected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2
- 4.7.0 and later · before 4.7.04063.05affected
Microsoft Microsoft .NET Framework 3.5 AND 4.8
- 4.8.0 and later · before 4.8.04667.03affected
Microsoft Microsoft .NET Framework 3.5 AND 4.8.1
- 4.8.1 and later · before 4.8.09186.01affected
Microsoft Microsoft .NET Framework 3.5.1
- 3.5.0 and later · before 3.0.30729.8957affected
Microsoft Microsoft .NET Framework 4.6.2
- 4.7.0 and later · before 4.7.04063.01affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| NuGet | Microsoft.NETCore.App.Runtime.win-arm64 | from 6.0.0 · before 6.0.22 | 6.0.22 |
| NuGet | Microsoft.NETCore.App.Runtime.win-arm64 | from 7.0.0 · before 7.0.11 | 7.0.11 |
| NuGet | Microsoft.NETCore.App.Runtime.win-x64 | from 6.0.0 · before 6.0.22 | 6.0.22 |
| NuGet | Microsoft.NETCore.App.Runtime.win-x64 | from 7.0.0 · before 7.0.11 | 7.0.11 |
| NuGet | Microsoft.NETCore.App.Runtime.win-x86 | from 6.0.0 · before 6.0.22 | 6.0.22 |
| NuGet | Microsoft.NETCore.App.Runtime.win-x86 | from 7.0.0 · before 7.0.11 | 7.0.11 |
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-36899Aug 8, 2023 · ASP.NET Elevation of Privilege Vulnerability58Plan
- ← EarlierCVE-2023-36788Sep 12, 2023 · .NET Framework Remote Code Execution Vulnerability31Monitor
- Later →CVE-2023-36793Sep 12, 2023 · Visual Studio Remote Code Execution Vulnerability31Monitor
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 |
|---|---|---|
| NuGet:Microsoft.NETCore.App.Runtime.win-arm64 | 6.0.22 | Package registry (OSV) |
| NuGet:Microsoft.NETCore.App.Runtime.win-arm64 | 7.0.11 | Package registry (OSV) |
| NuGet:Microsoft.NETCore.App.Runtime.win-x64 | 6.0.22 | Package registry (OSV) |
| NuGet:Microsoft.NETCore.App.Runtime.win-x64 | 7.0.11 | Package registry (OSV) |
| NuGet:Microsoft.NETCore.App.Runtime.win-x86 | 6.0.22 | Package registry (OSV) |
| NuGet:Microsoft.NETCore.App.Runtime.win-x86 | 7.0.11 | Package registry (OSV) |
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0520 · Sep 13, 2023(Visual Studio Güvenlik Zafiyeti)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.