CVE-2015-0071 — Microsoft Internet Explorer ASLR Bypass Vulnerability

CVE-2015-0071

Internet Explorer — ASLR Bypass via Crafted Web Page Enables Memory Layout Disclosure; Exploit Chain Enabler; Patched MS15-009

What Is ASLR in Internet Explorer?

Address Space Layout Randomization (ASLR) is a security mitigation that randomizes the memory addresses of executable code, stack, heap, and libraries each time a process starts. ASLR prevents attackers from reliably predicting where their shellcode or return-oriented programming (ROP) gadgets will be in memory — without knowing the layout, memory corruption exploits fail because the attacker cannot target a predictable address.

IE-specific ASLR bypasses are among the most valuable components of browser exploit chains. An ASLR bypass does not itself execute code — it leaks memory addresses that make a paired memory corruption exploit reliable. The CVSS score of 6.5 (Medium) understates operational impact because ASLR bypasses are essential enablers for fully weaponized browser exploitation.

Overview

Actively Exploited. This vulnerability has been added to CISA's Known Exploited Vulnerabilities (KEV) Catalog on May 25, 2022. Federal agencies are required to apply mitigations per BOD 22-01.

CVE-2015-0071 is an ASLR bypass vulnerability in Internet Explorer that allows a remote attacker, via a crafted web site, to discover memory addresses of IE modules or heap allocations. With the memory layout known, other IE vulnerabilities (memory corruption, use-after-free) that would otherwise fail due to address unpredictability become reliably exploitable. Patched in MS15-009 (February 10, 2015).

Affected Versions

Internet Explorer Status
IE 6 through 11 Vulnerable

Fixed in MS15-009 (February 2015 cumulative IE update).

Technical Details

Root Cause: Memory Address Disclosure

CVE-2015-0071 involves a code path in Internet Explorer that exposes internal memory address information to JavaScript or to a crafted DOM element in ways that bypass ASLR's address space randomization. When certain IE objects are created, manipulated, or queried, a pointer value or object address leaks into a context visible to an attacker's JavaScript.

A typical ASLR bypass attack flow:

  1. Attacker serves a malicious web page — the page contains JavaScript that triggers the leak condition
  2. IE leaks a memory address — a pointer to an IE module (e.g., mshtml.dll) or heap allocation is returned in a way the script can observe
  3. Attacker calculates base addresses — using the leaked address and known module layout, the attacker computes the full memory map of the IE process
  4. ROP chain succeeds — a paired RCE exploit (use-after-free, type confusion, etc.) uses the calculated addresses to build a working return-oriented programming chain that bypasses DEP/NX
  5. Full code execution achieved — the combined exploit delivers reliable code execution

Pairing With IE RCE Vulnerabilities

In February 2015, MS15-009 also patched multiple IE memory corruption vulnerabilities. ASLR bypasses are routinely combined with these in full exploit chains. Exploit kits (Angler, Nuclear, Magnitude) in this period maintained paired ASLR-bypass + RCE modules for IE.

Attack Characteristics

Attribute Detail
Attack Vector Network — user visits a malicious web page
Role in Exploit Chain ASLR bypass — enabler for RCE exploits
Alone Does not execute code; only leaks addresses
Combined Turns probabilistic exploits into reliable ones
Bulletin MS15-009 (February 2015)

Discovery

Reported to Microsoft and patched in the February 2015 cumulative Internet Explorer security update (MS15-009), which addressed both ASLR bypass and memory corruption vulnerabilities in IE 6 through 11.

Exploitation Context

  • Exploit kit integration: ASLR bypasses for IE were rapidly adopted by commercial exploit kits in 2015; Angler and Nuclear both maintained current IE ASLR bypass modules to maximize reliability of their IE memory corruption payloads
  • APT browser chains: Nation-state actors conducting watering hole attacks against targeted organizations used paired ASLR bypass + memory corruption chains for fully reliable browser-based compromise
  • CISA KEV (2022): Added May 2022, reflecting exploitation of the IE vulnerability class against unpatched legacy IE deployments

Remediation

CISA BOD 22-01 Deadline: June 15, 2022. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  1. Apply MS15-009 (February 2015 cumulative IE update).

  2. Retire Internet Explorer — Microsoft ended IE support June 15, 2022. No further patches exist for any IE vulnerability. Migrate to Microsoft Edge (Chromium) or another supported browser.

  3. Enable Enhanced Protected Mode (EPM) in IE 10/11 — EPM's AppContainer isolation limits the usefulness of ASLR bypass by adding further sandboxing even if memory addresses are leaked.

  4. Block IE via Group Policy or AppLocker if migration cannot be completed immediately.

Key Details

PropertyValue
CVE ID CVE-2015-0071
Vendor / Product Microsoft — Internet Explorer
NVD Published2015-02-11
NVD Last Modified2025-10-22
CVSS 3.1 Score6.5
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
SeverityMEDIUM
CWE CWE-200 — Exposure of Sensitive Information to an Unauthorized Actor find similar ↗
CISA KEV Added2022-05-25
CISA KEV Deadline2022-06-15
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Required Action

CISA BOD 22-01 Deadline: 2022-06-15. Apply updates per vendor instructions.

Timeline

DateEvent
2015-02-10Microsoft Security Bulletin MS15-009 released; CVE-2015-0071 patched
2015-02-11CVE-2015-0071 published by NVD
2022-05-25Added to CISA Known Exploited Vulnerabilities catalog
2022-06-15CISA BOD 22-01 remediation deadline