CVE Explore

Buffer overflow in Microsoft Edge

CVE-2017-0094

CVSS v3
7.5 High
Public exploits
None known
EPSS
0.290 · 98.2th percentile
Published
2017-03-17

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-0070, 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.

Vulnerability class: Buffer Overflow

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H.

Attack Vector
Network AV:N
Attack Complexity
High AC:H
Privileges Required
None PR:N
User Interaction
Required UI:R
Scope
Unchanged S:U
Confidentiality
High C:H
Integrity
High I:H
Availability
High A:H

EPSS exploit prediction

EPSS 0.290, 98.2th percentile (last changed ); down from 0.317 30 days earlier. About EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2017-0094: fell from 0.317 to 0.290.

EPSS over last 30 days · oldest: 0.317 · newest: 0.290 · change: -0.026

Affected products

Weakness classification (CWE)

Public exploits and proof-of-concept code

Also mentioned in 4 other repositories (ARPSyndicate/cvemon, lnick2023/nicenice, qazbnm456/awesome-cve-poc, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.

References