Skip to content
Fencer Intel
high 7.5

CVE-2017-0070 in the critical feed json

A remote code execution vulnerability exists in the way affected Microsoft scripting engines render when handling objects in memory in Micr…

published 2017-03-17 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-0437

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
76.7%
EPSS 76.7% chance of exploitation in 30 days, percentile 99.5%
public exploits
1
Exploit-DB

Summary

A remote code execution vulnerability exists in the way affected Microsoft scripting engines render when handling objects in memory in Microsoft browsers. These vulnerabilities could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. This vulnerability is different from those described in CVE-2017-0010, CVE-2017-0015, CVE-2017-0032, CVE-2017-0035, CVE-2017-0067, CVE-2017-0071, CVE-2017-0094, CVE-2017-0131, CVE-2017-0132, CVE-2017-0133, CVE-2017-0134, CVE-2017-0136, CVE-2017-0137, CVE-2017-0138, CVE-2017-0141, CVE-2017-0150, and CVE-2017-0151.

Patch / fix

Timeline

  1. First public exploit (EDB-41623)
  2. Published

Exploit prediction

76.73% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-41623 Microsoft Edge 38.14393.0.0 - JavaScript Engine Use-After-Free dos, 2017-03-16

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 7.6 AV:N/AC:H/Au:N/C:C/I:C/A:C

Affected products

  • Microsoft Corporation Browser

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.