A tampering vulnerability exists when .NET Core improperly handles specially crafted files, aka ".NET Core Tampering Vulnerability." This af
A tampering vulnerability exists when .NET Core improperly handles specially crafted files, aka ".NET Core Tampering Vulnerability." This affects .NET Core 2.1.
- Published
- Nov 13, 2018
- Updated
- Jun 16, 2026
- EPSS
- 7.3% · 94th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 7.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| microsoft | asp.net core | cpe:2.3:a:microsoft:asp.net_core |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft asp.net core2.1
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 Core
- 2.1affected
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 | from 2.1.0 · before 2.1.7 | 2.1.7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet | before 0:2.1.500-5.el7 | 0:2.1.500-5.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-debuginfo | before 0:2.1.500-5.el7 | 0:2.1.500-5.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-host | before 0:2.1.6-5.el7 | 0:2.1.6-5.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-runtime-2.1 | before 0:2.1.6-5.el7 | 0:2.1.6-5.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-sdk-2.1 | before 0:2.1.500-5.el7 | 0:2.1.500-5.el7 |
| Red Hat:rhel_dotnet:2.1::el7 | rh-dotnet21-dotnet-sdk-2.1.5xx | before 0:2.1.500-5.el7 | 0:2.1.500-5.el7 |
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-55315ASP.NET Security Feature Bypass Vulnerability59Plan
- CVE-2020-0603A remote code execution vulnerability exists in ASP.NET Core software when the software fails to handle objects in memory.An attacker who su41Plan
- CVE-2018-0787ASP.NET Core 1.0.38Monitor
- CVE-2017-11879ASP.NET Core 2.0 allows an attacker to steal log-in session information such as cookies or authentication tokens via a specially crafted URL38Monitor
- CVE-2018-0784ASP.NET Core 1.0.37Monitor
- CVE-2026-40372ASP.NET Core Elevation of Privilege Vulnerability36Monitor
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 | 2.1.7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet | 0:2.1.500-5.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-debuginfo | 0:2.1.500-5.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-host | 0:2.1.6-5.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-runtime-2.1 | 0:2.1.6-5.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-sdk-2.1 | 0:2.1.500-5.el7 · Red Hat:rhel_dotnet:2.1::el7 | Package registry (OSV) |
| red hat:rh-dotnet21-dotnet-sdk-2.1.5xx | 0:2.1.500-5.el7 · Red Hat:rhel_dotnet:2.1::el7 | 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).
Technical details
Attack conditions
- Anyone who can reach it over the internet 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
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.securityfocus.com/bid/105798
- www.securitytracker.com/id/1042128
- access.redhat.com/errata/RHSA-2018:3676
- portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8416
Vendor advisories and official records. Exploit/PoC links are deliberately left out.