CVE-2018-8373

What it actually does

The vulnerability corrupts memory in the Internet Explorer scripting engine while handling objects in memory, enabling remote code execution.

Why it matters to the business

Attackers can gain full control of affected systems, leading to data breaches or malware deployment. Listed on CISA KEV with a 2022 remediation deadline and high EPSS score indicates elevated real-world risk despite slight downward trend.

How an attack unfolds

An attacker crafts a malicious webpage exploiting the scripting engine object handling flaw; when rendered in vulnerable IE versions, memory corruption allows arbitrary code execution. Threat actor references point to Microsoft Scripting Engine Memory Corruption Vulnerability campaigns.

How to fix it

Apply security updates for Internet Explorer. For the listed affected packages upgrade to fixed versions: spring-projects/spring-security (GIT) to f154c7d9dcdebc690bf504b812db21a6d7148caf, org.springframework/spring-core (maven) to 4.2.12 / 5.0.12 / 5.1.5, org.springframework.security/spring-security-cas (maven) to 4.2.12.RELEASE / 5.0.12.RELEASE / 5.1.5.RELEASE, and org.springframework.security/spring-security-core (maven) to 4.2.12.RELEASE / 5.0.12.RELEASE / 5.1.5.RELEASE.

How to confirm the fix worked

Verify Internet Explorer is updated via Windows Update or Microsoft catalog; confirm Spring package versions match the listed fixed releases using dependency scanners or build manifests.

Typical attack path

1. Craft malicious HTML/JavaScript payload targeting object memory handling
2. Host the page on an attacker-controlled web server
3. Deliver the link via phishing email or compromised site
4. Victim visits the page using vulnerable Internet Explorer
5. Scripting engine memory corruption triggers remote code execution

How to detect it

Review web proxy and browser logs for visits to suspicious domains; inspect memory dumps or process crashes involving iexplore.exe related to scripting engine activity; correlate with known threat actor infrastructure from Microsoft Scripting Engine Memory Corruption Vulnerability campaigns.

What your security team should do

• Prioritize patching Internet Explorer immediately due to KEV listing and active exploitation
• Scan and upgrade all listed Spring dependencies to the exact fixed versions provided
• Disable Internet Explorer where possible or enforce Edge/Chrome via group policy
• Monitor EPSS trend and threat actor activity for changes in exploit availability