VYPR
High severityNVD Advisory· Published Sep 13, 2018· Updated Aug 5, 2024

CVE-2018-8465

CVE-2018-8465

Description

A memory corruption vulnerability in ChakraCore/Microsoft Edge allows remote code execution via a crafted website.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A memory corruption vulnerability in ChakraCore/Microsoft Edge allows remote code execution via a crafted website.

Vulnerability

A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge [1]. This affects Microsoft Edge and ChakraCore [1]. The vulnerability is a memory corruption issue that occurs when the scripting engine improperly handles objects in memory [2]. Affected versions include Microsoft Edge on various Windows 10 builds and ChakraCore prior to security updates provided in September 2018 [2][4].

Exploitation

An attacker who successfully exploited this vulnerability could gain the same user rights as the current user [1]. Exploitation requires that a user visit a specially crafted website using Microsoft Edge, or open a specially crafted file that invokes the vulnerable code path [2][3]. The attacker can host the website or inject the malicious content into a compromised site [3]. No authentication is required; the attacker only needs to convince the user to view the crafted content [2].

Impact

Successful exploitation allows remote code execution in the context of the current user [1]. The attacker can then install programs, view, change, or delete data, or create new accounts with full user rights [1]. The impact is limited to the privileges of the user running Edge; if the user has administrative rights, the attacker could take complete control of the affected system [2].

Mitigation

Microsoft released security updates on September 11, 2018, which addressed this vulnerability [3]. Users should apply the latest Windows and Edge updates [3]. ChakraCore users should update to the patched version [4]. No workaround is available beyond applying the patch [3].

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
Microsoft.ChakraCoreNuGet
< 1.11.11.11.1

Affected products

3

Patches

1
7e235c914df5

[CVE-2018-8465] Chakra - Invalid stack read leads to type confusion - Individual

https://github.com/chakra-core/ChakraCoreMatt GardnerSep 10, 2018via ghsa
2 files changed · +7 1
  • lib/Backend/arm64/LowerMD.cpp+2 1 modified
    @@ -1129,7 +1129,8 @@ ARM64StackLayout::ARM64StackLayout(Func* func)
             // the worst case assumption (homing all NUM_INT_ARG_REGS).
             this->m_hasCalls = func->GetHasCalls() ||
                 func->HasAnyStackNestedFunc() || 
    -            !LowererMD::IsSmallStack(this->TotalStackSize() + NUM_INT_ARG_REGS * MachRegInt);
    +            !LowererMD::IsSmallStack(this->TotalStackSize() + NUM_INT_ARG_REGS * MachRegInt) ||
    +            Lowerer::IsArgSaveRequired(func);
     
             // Home the params. This is done to enable on-the-fly creation of the arguments object,
             // Dyno bailout code, etc. For non-global functions, that means homing all the param registers
    
  • lib/Backend/arm/LowerMD.cpp+5 0 modified
    @@ -1108,6 +1108,11 @@ LowererMD::LowerEntryInstr(IR::EntryInstr * entryInstr)
             unwindInfo->SetHasCalls(true);
         }
     
    +    if (Lowerer::IsArgSaveRequired(this->m_func))
    +    {
    +        unwindInfo->SetHasCalls(true);
    +    }
    +
         bool hasCalls = unwindInfo->GetHasCalls();
     
         // Home the params. This is done to enable on-the-fly creation of the arguments object,
    

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

9

News mentions

0

No linked articles in our index yet.