NVD / CVE Program· CNA microsoft

CVE-2019-1142: An elevation of privilege vulnerability exists when the .NET Framework common language runtime (CLR) allows file creation in arbitrary locat

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% (FIRST EPSS); higher than 63.7% 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.

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 the .NET Framework common language runtime (CLR) allows file creation in arbitrary locations, aka '.NET Framework Elevation of Privilege Vulnerability'.

MediumCVSS 5.5 · v3.1—No exploit No fix recorded

BDU:2019-03166

Published: Sep 11, 2019
Updated: Jun 16, 2026
EPSS: 1.0% · 63th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.0%

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

Is your version affected? Check it

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 help

Affected 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.

ProductVersion

Vendor	Product	CPE
microsoft	.net framework	cpe:2.3:a:microsoft:.net_framework
microsoft	windows 10	cpe:2.3:o:microsoft:windows_10
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 server 2016	cpe:2.3:o:microsoft:windows_server_2016
microsoft	windows server 2019	cpe:2.3:o:microsoft:windows_server_2019
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 framework3.5
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 3.5
- Windows Server 2012, Windows Server 2012 (Server Core installation), Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), Windows 10 for 32-bit Systems, Windows 10 for x64-based Systems, Windows Server 2016, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows Server 2016 (Server Core installation) … (+7)affected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation)
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 (Server Core installation)
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 1903 (Server Core installation)
- 1903affected

Same product

microsoft: all records

Other 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 KEV
99Now
CVE-2024-29059.NET Framework Information Disclosure VulnerabilityKEV
90Now
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 documeKEV
88Now

Published before and after this one in the same product

← EarlierCVE-2019-1083Jul 15, 2019 · A denial of service vulnerability exists when Microsoft Common Object Runtime Library improperly handles web requests, aka '.NET Denial of S
32Monitor
← EarlierCVE-2019-1113Jul 15, 2019 · A remote code execution vulnerability exists in .NET software when the software fails to check the source markup of a file.An attacker who s
38Monitor
Later →CVE-2020-0605Jan 14, 2020 · A remote code execution vulnerability exists in .NET software when the software fails to check the source markup of a file.An attacker who s
40Plan

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.

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

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: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

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

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1142

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

All records