Skip to content
Noroxi
CVE-2021-24112· NVD / CVE Program· CNA microsoft

.NET Core Remote Code Execution Vulnerability

HighCVSS 8.1 · v3.1—No exploit Fix available
Published
Feb 25, 2021
Updated
Jun 16, 2026
EPSS
3.3% · 88th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.3%

CNA vs NVD score

NVD
—
CNA · microsoft
8.1
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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 help

Affected systems

VendorProduct
microsoft.net
microsoft.net core
microsoftmono
microsoftvisual studio 2019

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • microsoft .net5.0 and later · up to 5.0.2 inclusive
  • microsoft .net core2.1 and later · up to 2.1.24 inclusive
  • microsoft .net core3.1 and later · up to 3.1.11 inclusive
  • microsoft mono6.12.0 and later · before 6.12.0.122
  • microsoft visual studio 2019all versions

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 5.0

    • 5.0.0 and later · before publicationaffected

  • Microsoft .NET Core 2.1

    • 2.1 and later · before publicationaffected

  • Microsoft .NET Core 3.1

    • 3.1 and later · before publicationaffected

  • Microsoft Mono 6.12.0

    • 6.12.0 and later · before publicationaffected

  • Microsoft Visual Studio 2019 for Mac

    • 8.0.0 and later · before publicationaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
NuGetSystem.Drawing.Commonfrom 4.0.0 · before 4.7.24.7.2
NuGetSystem.Drawing.Commonfrom 5.0.0 · before 5.0.35.0.3

Same product

microsoft: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-38180.NET and Visual Studio Denial of Service VulnerabilityKEV
    64This week
  • CVE-2023-38171Microsoft QUIC Denial of Service Vulnerability
    51Plan
  • CVE-2021-26701.NET Core Remote Code Execution Vulnerability
    41Plan
  • CVE-2024-43498.NET and Visual Studio Remote Code Execution Vulnerability
    40Plan
  • CVE-2025-21176.NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability
    36Monitor
  • CVE-2026-69439.NET and Visual Studio Elevation of Privilege Vulnerability
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
NuGet:System.Drawing.Common4.7.2Package registry (OSV)
NuGet:System.Drawing.Common5.0.3Package 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.

EPSS, last 120 days

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 researchers

Finders, 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.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

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
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records