BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2017
CVE-2017-8598High confidence

Microsoft Corporation Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016: Improper Restriction of Operations within the Bounds of a Memory Buffer

Microsoft Corporation · Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016

7.5HighCVSS 3.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2017-17547

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

Microsoft Edge in Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user when the JavaScript engine fails to render when handling objects in memory in Microsoft Edge, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8596, CVE-2017-8610, CVE-2017-8618, CVE-2017-8619, CVE-2017-8595, CVE-2017-8601, CVE-2017-8603, CVE-2017-8604, CVE-2017-8605, CVE-2017-8606, CVE-2017-8607, CVE-2017-8608, and CVE-2017-8609.

What

Microsoft Edge in Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user when the JavaScript engine fails to render when handling objects in memory in Microsoft Edge, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8596, CVE-2017-8610, CVE-2017-8618, CVE-2017-8619, CVE-2017-8595, CVE-2017-8601, CVE-2017-8603, CVE-2017-8604, CVE-2017-8605, CVE-2017-8606, CVE-2017-8607, CVE-2017-8608, and CVE-2017-8609.

Why

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

What

Microsoft Edge in Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user when the JavaScript engine fails to render when handling objects in memory in Microsoft Edge, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8596, CVE-2017-8610, CVE-2017-8618, CVE-2017-8619, CVE-2017-8595, CVE-2017-8601, CVE-2017-8603, CVE-2017-8604, CVE-2017-8605, CVE-2017-8606, CVE-2017-8607, CVE-2017-8608, and CVE-2017-8609.

Why

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Restriction of Operations within the Bounds of a Memory Buffer → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-119 ↗

CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer. The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-119
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Canadian Centre for Cyber Security · English · AV17-100Microsoft security updates

s and Web Apps, .NET Framework, Adobe Flash Player, Microsoft Exchange Server. CVE References: CVE-2017-0170, CVE-2017-0243, CVE-2017-8463, CVE-2017-8467, CVE-2017-8486, CVE-2017-8495, CVE-2017-8501, CVE-2017-8502, CVE-2017-8556, CVE-2017-8557, CVE-2017-8559, CVE-2017-8560, CVE-2017-8561, CVE-2017-8562, CVE-2017-8563, CVE-2017-8564, CVE-2017-8565, CVE-2017-8566, CVE-2017-8569, CVE-2017-8570, CVE-2017-8573, CVE-2017-8574, CVE-2017-8577, CVE-2017-8578, CVE-2017-8580, CVE-2017-8581, CVE-2017-8582, CVE-2017-8584, CVE-2017-8585, CVE-2017-8587, CVE-2017-8588, CVE-2017-8589, CVE-2017-8590, CVE-2017-8592, CVE-2017-8594, CVE-2017-8595, CVE-2017-8596, CVE-2017-8598, CVE-2017-8599, CVE-2017-8601, CVE-2017-8602, CVE-2017-8603, CVE-2017-8604, CVE-2017-8605, CVE-2017-8606, CVE-2017-8607, CVE-2017-8608, CVE-2017-8609, CVE-2017-8610, CVE-2017-8611, CVE-2017-8617, CVE-2017-8618, CVE-2017-8619, CVE-2017-8621 Suggested Action CCIRC recommends that system administrators test and deploy the vendor-released updates to affected applications accordingly. References: https://portal.msrc.microsoft.com/en-us/security-guidance/releasenotedetail/f2b16606-4945-e711-80dc-000d3a32fc99

Official advisory ↗
CERT-FR · French · CERTFR-2017-AVI-206Multiples vulnérabilités dans Microsoft Edge

De multiples vulnérabilités ont été corrigées dans Microsoft Edge . Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance et un contournement de la politique de sécurité.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005128耇数の Microsoft Windows 補品の Internet Explorer 9 から 11 および Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

耇数の Microsoft Windows 補品の Microsoft Internet Explorer 9 から 11 および Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「スクリプト ゚ンゞンのメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8598、CVE-2017-8596、CVE-2017-8610、CVE-2017-8601、CVE-2017-8618、CVE-2017-8619、CVE-2017-8603、CVE-2017-8604、CVE-2017-8605、CVE-2017-8595、CVE-2017-8606、CVE-2017-8607、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005127耇数の Microsoft Windows 補品の Internet Explorer 9 から 11 および Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

耇数の Microsoft Windows 補品の Microsoft Internet Explorer 9 から 11 および Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「スクリプト ゚ンゞンのメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8598、CVE-2017-8596、CVE-2017-8618、CVE-2017-8619、CVE-2017-8610、CVE-2017-8601、CVE-2017-8603、CVE-2017-8604、CVE-2017-8605、CVE-2017-8595、CVE-2017-8606、CVE-2017-8608、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005126耇数の Microsoft Windows 補品の Internet Explorer 9 から 11 および Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

耇数の Microsoft Windows 補品の Microsoft Internet Explorer 9 から 11 および Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「スクリプト ゚ンゞンのメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8598、CVE-2017-8596、CVE-2017-8618、CVE-2017-8619、CVE-2017-8610、CVE-2017-8601、CVE-2017-8603、CVE-2017-8604、CVE-2017-8605、CVE-2017-8595、CVE-2017-8607、CVE-2017-8608、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005107Microsoft Windows 10 の Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

Microsoft Windows 10 1703 の Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「スクリプト ゚ンゞンのメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8598、CVE-2017-8596、CVE-2017-8595、CVE-2017-8618、CVE-2017-8619、CVE-2017-8601、CVE-2017-8603、CVE-2017-8604、CVE-2017-8605、CVE-2017-8606、CVE-2017-8607、CVE-2017-8608、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005106Microsoft Windows 10 および Windows Server 2016 の Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

Microsoft Windows 10 Gold、1511、1607、1703、および Windows Server 2016 の Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「スクリプト ゚ンゞンのメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8596、CVE-2017-8601、CVE-2017-8618、CVE-2017-8619、CVE-2017-8610、CVE-2017-8601、CVE-2017-8603、CVE-2017-8604、CVE-2017-8598、CVE-2017-8606、CVE-2017-8607、CVE-2017-8608、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005105Microsoft Windows 10 および Windows Server 2016 の Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

Microsoft Windows 10 1511、1607、1703、および Windows Server 2016 の Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「スクリプト ゚ンゞンのメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8596、CVE-2017-8618、CVE-2017-8619、CVE-2017-8601、CVE-2017-8610、CVE-2017-8603、CVE-2017-8598、CVE-2017-8601、CVE-2017-8605、CVE-2017-8606、CVE-2017-8607、CVE-2017-8608、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005104Microsoft Windows 10 および Windows Server 2016 の Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

Microsoft Windows 10 1511、1607、1703、および Windows Server 2016 の Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「スクリプト ゚ンゞンのメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8596、CVE-2017-8610、CVE-2017-8598、CVE-2017-8618、CVE-2017-8619、CVE-2017-8595、CVE-2017-8601、CVE-2017-8604、CVE-2017-8605、CVE-2017-8606、CVE-2017-8607、CVE-2017-8608、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005103Microsoft Windows 10 および Windows Server 2016 の Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

Microsoft Windows 10 Gold、1511、1607、1703、および Windows Server 2016 の Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「スクリプト ゚ンゞンのメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8596、CVE-2017-8610、CVE-2017-8618、CVE-2017-8619、CVE-2017-8603、CVE-2017-8604、CVE-2017-8605、CVE-2017-8606、CVE-2017-8607、CVE-2017-8608、CVE-2017-8598、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005102Microsoft Windows 10 および Windows Server 2016 の Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

Microsoft Windows 10 Gold、1511、1607、1703、および Windows Server 2016 の Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「スクリプト ゚ンゞンのメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8596、CVE-2017-8610、CVE-2017-8618、CVE-2017-8619、CVE-2017-8595、CVE-2017-8601、CVE-2017-8603、CVE-2017-8604、CVE-2017-8605、CVE-2017-8606、CVE-2017-8607、CVE-2017-8608、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-005101Microsoft Windows 10 および Windows Server 2016 の Microsoft Edge における珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性

Microsoft Windows 10 1607、1703、および Windows Server 2016 の Microsoft Edge には、メモリ内のオブゞェクトの凊理の際に JavaScript ゚ンゞンがレンダリングに倱敗する堎合、珟圚のナヌザのコンテキストで任意のコヌドを実行される脆匱性が存圚したす。 ベンダは、本脆匱性を「Microsoft Edge のメモリ砎損の脆匱性」ずしお公開しおいたす。 本脆匱性は、CVE-2017-8598、CVE-2017-8610、CVE-2017-8595、CVE-2017-8601、CVE-2017-8603、CVE-2017-8604、CVE-2017-8605、CVE-2017-8606、CVE-2017-8607、CVE-2017-8608、および CVE-2017-8609 ずは異なる脆匱性です。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016: Microsoft Edge
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 11 Jul 2017 · Last source change 16 Sept 2024, 16:13 UTC · CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2017-17547
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to authoritative remediation link · patch.
    Before
    no authoritative guidance recorded
    After
    authoritative remediation link · patch
    af854a3a-2127-422b-91ae-364da2661108 ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    Microsoft Edge · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Microsoft Edge · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    af854a3a-2127-422b-91ae-364da2661108 ↗
  4. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    NIST NVD ↗
  5. CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    7.5 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H)
    NIST NVD ↗
  6. ENISA EUVD mappingEUVD-2017-17547 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2017-17547"}
    ENISA EUVD ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2017-17547↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2017-8598 · cve.blacktree.nl