Microsoft · .NET · CWE-416 · published 2014-04-27
CVE-2014-1776Microsoft Internet Explorer Memory Corruption Vulnerability
Patch today Known exploited server software, exploitation is automatable, total technical impact.
CVE-2014-1776 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2022-01-28. EPSS estimates an 82.7% chance of exploitation in the next 30 days, higher than 99% of all CVEs. This .NET vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. CISA’s required action: Apply updates per vendor instructions. US federal agencies must remediate by 2022-07-28. Patch today.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA required action: Apply updates per vendor instructions. (federal due date 2022-07-28)
Patch events
Language runtime.NET
Memory CorruptionCVE-2014-1776
Why: Known exploited server software, exploitation is automatable, total technical impact.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2022-01-28 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 83% (100th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-416: Use After Free
More from this vendor: all Microsoft vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Product
n/a(affected)
Description (from the CVE record)#
Use-after-free vulnerability in Microsoft Internet Explorer 6 through 11 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via vectors related to the CMarkup::IsConnectedToPrimaryMarkup function, as exploited in the wild in April 2014. NOTE: this issue originally emphasized VGX.DLL, but Microsoft clarified that "VGX.DLL does not contain the vulnerable code leveraged in this exploit. Disabling VGX.DLL is an exploit-specific workaround that provides an immediate, effective workaround to help block known attacks."
Quoted from the CVE Program record.