LiveActive security incident?Get immediate response
CVE Record

CVE-2017-0152: A remote code execution vulnerability exists in the way affected Microsoft scripting engine render when han...

A remote code execution vulnerability exists in the way affected Microsoft scripting engine render when handling objects in memory in Microsoft browsers. The vulnerability 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, aka "Scripting Engine Memory Corruption Vulnerability."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Microsoft scripting engine memory corruption issue that could let a malicious web page execute code as the signed-in user. Business impact depends on whether affected ChakraCore or Microsoft browser components are still present or supported in the environment.

Executive priority

Prioritize confirmation and patch status where legacy Microsoft browser or ChakraCore components remain in use. Treat confirmed exposure as urgent because the impact is code execution as the current user, even though exploitation evidence is not provided here.

Technical view

The CVE describes remote code execution caused by memory corruption while the Microsoft scripting engine handles objects in memory. Successful exploitation would run arbitrary code in the current user's context. The bundle identifies Microsoft ChakraCore and cites a ChakraCore commit, but does not provide CVSS, precise versions, or advisory details.

Likely exposure

Exposure is most likely on systems or applications using affected Microsoft ChakraCore or Microsoft browser scripting components. The provided sources do not define exact vulnerable versions, deployment modes, or whether downstream products were affected.

Exploitation context

The source bundle does not show CISA KEV listing and provides no cited evidence of active exploitation. The described attack context is browser or scripting-engine content handling, but the sources do not include exploit maturity or public weaponization status.

Researcher notes

Key gaps are missing CVSS, exact affected versions, and formal remediation text in the supplied bundle. Use the CVE record and Microsoft ChakraCore commit as starting evidence, then verify product scope against Microsoft advisories before asserting exposure.

Mitigation direction

  • Check Microsoft guidance for CVE-2017-0152 and related ChakraCore releases.
  • Update affected ChakraCore or browser components to versions containing the referenced vendor fix.
  • Reduce exposure to untrusted web content on systems that cannot be updated.
  • Run affected software with least-privilege user accounts where possible.

Validation and detection

  • Inventory systems and applications using Microsoft ChakraCore or affected Microsoft browser components.
  • Compare installed component versions against Microsoft guidance and the referenced ChakraCore commit lineage.
  • Confirm endpoint patch records cover the relevant Microsoft browser or scripting engine updates.
  • Document any unsupported systems requiring compensating controls.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-0152 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Microsoft CorporationMicrosoft ChakraCoreMicrosoft ChakraCoreListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.