CVE-2020-1476: ASP.NET and .NET Elevation of Privilege Vulnerability
Noroxi assessment
Priority: Monitor (action score 22/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.1% (FIRST EPSS); higher than 66.3% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- 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
An elevation of privilege vulnerability exists when ASP.NET or .NET web applications running on IIS improperly allow access to cached files. An attacker who successfully exploited this vulnerability could gain access to restricted files. To exploit this vulnerability, an attacker would need to send a specially crafted request to an affected server. The update addresses the vulnerability by changing how ASP.NET and .NET handle requests.
- Published
- Aug 17, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
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.
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 8.1 | cpe:2.3:o:microsoft:windows_8.1 |
| microsoft | windows server 2012 | cpe:2.3:o:microsoft:windows_server_2012 |
| microsoft | windows 10 | cpe:2.3:o:microsoft:windows_10 |
| microsoft | windows server 2016 | cpe:2.3:o:microsoft:windows_server_2016 |
| microsoft | windows server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
| microsoft | windows 7 | cpe:2.3:o:microsoft:windows_7 |
| microsoft | windows rt 8.1 | cpe:2.3:o:microsoft:windows_rt_8.1 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft .net framework2.0
- microsoft .net framework3.5
- microsoft .net framework3.5.1
- microsoft .net framework4.5.2
- microsoft .net framework4.6
- microsoft .net framework4.6.1
- microsoft .net framework4.6.2
- microsoft .net framework4.7
- microsoft .net framework4.7.1
- microsoft .net framework4.7.2
- microsoft .net framework4.8
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 Microsoft .NET Framework 2.0 Service Pack 2
- 2.0.0 and later · before publicationaffected
Microsoft Microsoft .NET Framework 3.5
- 3.5.0 and later · before publicationaffected
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 publicationaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.6/4.6.1/4.6.2
- 3.5.0 and later · before publicationaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.1/4.7.2
- 3.0 and later · before publicationaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2
- 4.7.0 and later · before publicationaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8
- 4.8.0 and later · before publicationaffected
Microsoft Microsoft .NET Framework 3.5.1
- 3.5.0 and later · before publicationaffected
Microsoft Microsoft .NET Framework 4.5.2
- 4.0.0.0 and later · before publicationaffected
Microsoft Microsoft .NET Framework 4.6
- 4.0.0.0 and later · before publicationaffected
Microsoft Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2
- 4.0.0.0 and later · before publicationaffected
Microsoft Microsoft .NET Framework 4.8
- 4.8.0 and later · before publicationaffected
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-2020-1066May 21, 2020 · .NET Framework Elevation of Privilege Vulnerability32Monitor
- ← EarlierCVE-2020-1046Aug 17, 2020 · .NET Framework Remote Code Execution Vulnerability32Monitor
- Later →CVE-2020-16937Oct 16, 2020 · .NET Framework Information Disclosure Vulnerability19Monitor
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.
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-597 · Aug 12, 2020(Microsoft Ağustos 2020 Güvenlik Güncellemelerini Yayınladı)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
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
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.