CVE-2020-1062

7.5 HIGH

📋 TL;DR

This CVE describes a remote code execution vulnerability in Internet Explorer due to improper memory access, allowing attackers to corrupt memory and potentially execute arbitrary code. It affects users running vulnerable versions of Internet Explorer on Windows systems, primarily those who browse untrusted or malicious websites.

💻 Affected Systems

Products:
  • Internet Explorer
Versions: Affected versions include Internet Explorer 11 and earlier on supported Windows releases; specific details are in the Microsoft advisory.
Operating Systems: Windows 10, Windows 8.1, Windows 7, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2008 R2
Default Config Vulnerable: ⚠️ Yes
Notes: Systems with Internet Explorer enabled and not patched are vulnerable; using alternative browsers may reduce exposure.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker could exploit this to execute arbitrary code with the privileges of the current user, leading to full system compromise, data theft, or malware installation.

🟠

Likely Case

In real-world scenarios, attackers might use this to deliver malware or ransomware via malicious websites, compromising user systems and potentially spreading within networks.

🟢

If Mitigated

With proper controls like patching, disabling Internet Explorer, or using application whitelisting, the risk is significantly reduced, limiting exploitation to isolated incidents.

🌐 Internet-Facing: HIGH, as Internet Explorer is commonly used for web browsing, making systems vulnerable to attacks from malicious websites or ads.
🏢 Internal Only: MEDIUM, as internal users might still encounter malicious content via emails or intranet sites, but network segmentation can reduce spread.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation typically requires user interaction, such as visiting a malicious website, but no public proof-of-concept has been confirmed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply the security update from Microsoft's May 2020 Patch Tuesday or later; specific KB numbers are in the advisory.

Vendor Advisory: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1062

Restart Required: Yes

Instructions:

1. Open Windows Update settings. 2. Check for updates and install the latest security patches. 3. Restart the system if prompted. For enterprise environments, use WSUS or SCCM to deploy updates.

🔧 Temporary Workarounds

Disable Internet Explorer

windows

Disable Internet Explorer to prevent exploitation by using alternative browsers like Microsoft Edge.

Optional: Use Group Policy to disable IE via Computer Configuration > Administrative Templates > Windows Components > Internet Explorer > Disable Internet Explorer.

Enable Enhanced Security Configuration

windows

Configure Internet Explorer to run in Enhanced Security Mode to restrict script execution and reduce attack surface.

In IE, go to Tools > Internet Options > Security tab, set zones to High security, or use Group Policy for enforcement.

🧯 If You Can't Patch

  • Disable Active Scripting in Internet Explorer zones to block malicious scripts from executing.
  • Implement network segmentation and web filtering to block access to known malicious websites and reduce exposure.

🔍 How to Verify

Check if Vulnerable:

Check the installed Windows updates for the May 2020 security patches; if missing, the system is likely vulnerable. Use 'wmic qfe list' in Command Prompt to list updates.

Check Version:

In Internet Explorer, go to Help > About Internet Explorer to check the version; vulnerable versions are 11 and earlier on affected OSes.

Verify Fix Applied:

Verify that the security update KB4550961 or later is installed; check via Control Panel > Programs > View installed updates or use 'Get-Hotfix -Id KB4550961' in PowerShell.

📡 Detection & Monitoring

Log Indicators:

  • Look for crash logs or unexpected process terminations in Internet Explorer (e.g., Event ID 1000 in Windows Application logs).
  • Monitor for suspicious script execution or memory access errors in security logs.

Network Indicators:

  • Detect outbound connections to known malicious IPs or domains after visiting suspicious websites.
  • Use network intrusion detection systems to flag anomalous HTTP traffic patterns.

SIEM Query:

Example: 'source="Windows Security" event_id=4688 process_name="iexplore.exe" AND command_line CONTAINS "suspicious"' for process creation alerts.

🔗 References

📤 Share & Export