CVE-2019-1113
No exploitation reported by the sources we read.
- Published2019-07-15
- WeaknessCWE-20
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A remote code execution vulnerability exists in .NET software when the software fails to check the source markup of a file.An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user, aka '.NET Framework Remote Code Execution Vulnerability'.
Timeline
dates in UTC- 2019-07-1519:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-1113?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-1113?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.0 | = 2.0 | no fix published | NVD |
| 3.0 | = 3.0 | no fix published | NVD |
| 3.5 | = 3.5 | no fix published | NVD |
| 4.7 | = 4.7.2 | no fix published | NVD |
| 4.8 | = 4.8 | no fix published | NVD |
| 3.5 | = 3.5.1 | no fix published | NVD |
| 4.5 | = 4.5.2 | no fix published | NVD |
| 4.6 | = 4.6 | no fix published | NVD |
| 4.6 | = 4.6.1 | no fix published | NVD |
| 4.6 | = 4.6.2 | no fix published | NVD |
| 4.7 | = 4.7 | no fix published | NVD |
| 4.7 | = 4.7.1 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | all versions | no fix published | NVD |
| 15.9 | = 15.9 | no fix published | NVD |
| 16.0 | = 16.0 | no fix published | NVD |
| 16.1 | = 16.1 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- portal.msrc.microsoft.comPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.08.8read 2026-10-23
- NVDCVSS 2.06.8read 2026-10-23
- NVDweakness (CWE)CWE-20read 2026-10-23
- FIRST EPSSEPSS score10.0 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2019-07-15
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-1113?
Is CVE-2019-1113 actively exploited?
What is the CVSS score for CVE-2019-1113?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.