Outdated .NET Framework or .NET Runtime

Hosts run .NET Framework or .NET runtimes that are missing Microsoft security updates or have reached end of support.

SeverityHigh
CVSS 3.18.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.09.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1395: Dependency on Vulnerable Third-Party Component
OWASP Top 10A03:2025 Software Supply Chain Failures
MITRE ATT&CKT1190 Exploit Public-Facing Application, T1203 Exploitation for Client Execution, T1499.004 Application or System Exploitation
CategoryOutdated Components

Description

One or more hosts have .NET Framework or .NET (formerly .NET Core) runtimes that are missing security updates, or .NET runtimes from release lines that have passed the end of their support and receive no further fixes. .NET Framework is a component of Windows and receives monthly security updates through Windows Update and WSUS. .NET runtimes are installed separately and side by side, often several versions on one host, and each release line is supported for a fixed period; Microsoft releases their security updates on Patch Tuesday, and they reach hosts only if Microsoft Update or another deployment tool installs them. Applications published as self-contained carry their own copy of the runtime and are fixed only when the application is rebuilt.

The impact depends on which runtime is affected and how it is used. Past .NET vulnerabilities include remote code execution, denial of service and request smuggling in ASP.NET Core and its Kestrel web server, security feature bypass and elevation of privilege. Flaws in ASP.NET Core and the runtime libraries can let an unauthenticated attacker take down or, in some cases, compromise a web application running on the vulnerable runtime, while flaws in .NET Framework have allowed code execution when a user opens a crafted file, or elevation of privilege on the host.

The finding is identified by authenticated scans that read installed runtime and file versions, or with dotnet --list-runtimes, and scanners report one result per missing update or unsupported runtime. Old runtimes are often left behind after an application moves to a newer one and remain installed but unused; they present little direct risk, although they remain on the host and are reported by every scan.

Remediation

Update the runtimes in use and remove the rest:

  • Install the latest .NET Framework updates through Windows Update, WSUS or the patch management tool as part of the monthly Windows update cycle.
  • Install the latest patch release for every supported .NET and ASP.NET Core runtime in use, and enable Microsoft Update or the organisation's deployment tooling so that future updates arrive automatically.
  • Move applications on release lines past end of support to a supported one, preferably a long-term support release, then uninstall the old runtimes.
  • Rebuild and redeploy self-contained applications and container images with the latest runtime patch.
  • Uninstall runtimes and SDKs that no application uses.

Confirm the fix with dotnet --list-runtimes and the host's update history, and by repeating the scan.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Patching and Outdated Software Findings

Every Patching and Outdated Software finding