LiveActive security incident?Get immediate response
CVE Record

CVE-2018-8177: A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in...

A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka "Chakra Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore. This CVE ID is unique from CVE-2018-0943, CVE-2018-8130, CVE-2018-8133, CVE-2018-8145.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2018-8177 is a Microsoft Chakra scripting engine memory corruption issue that can allow remote code execution. Business risk is highest where legacy Microsoft Edge or ChakraCore-based software remains in use. The source bundle does not provide CVSS, fixed versions, or named mitigations, so remediation should be driven by Microsoft guidance. Exposure is likely limited to environments running affected Microsoft Edge Chakra components or ChakraCore. Modern inventories should specifically check for legacy Edge dependencies, embedded ChakraCore use, and unsupported systems that may have missed the 2018 Microsoft advisory cycle. Prioritize as high if legacy Microsoft browser technology or ChakraCore exists in the estate. If inventories show no affected runtime, document that evidence and monitor for unsupported software reintroduction. Mitigation focus: Review the Microsoft MSRC advisory for supported fixes and product-specific guidance.; Update or retire affected Microsoft Edge or ChakraCore deployments per vendor guidance.; Remove unsupported legacy browser/runtime dependencies where business workflows allow..

Prepared

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-2018-8177 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
MicrosoftChakraCoreChakraCoreListed
Weakness

CWE details

No CWE listed

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