Cyber Resilience

CVE-2010-0248

RCE in Microsoft Internet Explorer 6 … 8.0.6001

High EPSSRCEMemory Safety
Published
22 January 2010
Modified
11 April 2025
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.53 99th percentile
Risk Priority 81 floored blend · peak EPSS

Summary

CVE-2010-0248 is a high-severity Code Injection (CWE-94) vulnerability in Microsoft Internet Explorer. Its CVSS base score is 8.1 (High).

Operationally, ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Microsoft Internet Explorer 6, 6 SP1, 7, and 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to…

more

memory corruption, aka "HTML Object Memory Corruption Vulnerability."

CWE(s)
CWE-94CWE-416

Related Threats

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1203 Exploitation for Client Execution Executionconfidence: HIGH
Memory corruption via use-after-free or uninitialized object in IE enables client-side code execution when rendering attacker-controlled HTML.
attack.mitre.org →
T1189 Drive-by Compromise Initial Accessconfidence: HIGH
The vulnerability is triggered by visiting a malicious webpage, constituting a drive-by compromise.
attack.mitre.org →
T1059.007 JavaScript Executionconfidence: MEDIUM
Arbitrary code execution achieved through crafted JavaScript/HTML in the browser context.
attack.mitre.org →
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2010-0249Same product: Microsoft Internet Explorer
CVE-2010-0806Same product: Microsoft Internet Explorer
CVE-2010-3962Same product: Microsoft Internet Explorer
CVE-2012-4969Same product: Microsoft Internet Explorer
CVE-2012-4792Same product: Microsoft Internet Explorer
CVE-2013-1347Same product: Microsoft Internet Explorer
CVE-2008-4250Same product: Microsoft Windows 2000
CVE-2013-2551Same product: Microsoft Internet Explorer
CVE-2013-0810Same product: Microsoft Windows Server 2003
CVE-2013-3897Same product: Microsoft Internet Explorer

Affected Assets

microsoft
internet explorer
6, 6.0, 6.0.2600, 6.0.2800, 6.0.2800.1106

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.4.3
  • V1.3.1

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SI-16 Memory Protection
addresses: CWE-94 CWE-416

Directly prevents execution of attacker-supplied code written into data memory regions.

SC-34 Non-modifiable Executable Programs
addresses: CWE-94

Makes persistent code injection into loaded programs impossible when the executable image itself resides on hardware-protected read-only media.

SC-44 Detonation Chambers
addresses: CWE-94

Dynamically generated code can be produced and executed inside the isolated chamber, preventing host compromise from code-injection payloads.

SI-10 Information Input Validation
addresses: CWE-94

Validates inputs used in dynamic code generation to block injected directives.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

PR.PS-06's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.

PR.PS-02 partial match
prevents

Routine patching removes known use-after-free instances after they have been introduced in released software.

PR.DS-10 none match
prevents

PR.DS-10 protects runtime data confidentiality/integrity but has no bearing on neutralizing externally influenced input during code generation, so neither direction shows any preventive effect.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect use-after-free bugs before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates memory-safety practices that reduce use-after-free defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-management rules that mitigate use-after-free.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include memory-safety design choices that limit use-after-free exposure.

A.8.28 Secure coding partial match
prevents

Banning unapproved code samples and unauthenticated web services, combined with secure-coding standards and SAST, prevents the dynamic generation or inclusion of attacker-supplied code.

A.8.32 Change management partial match
prevents

Change-management processes help ensure memory-safety fixes are deployed consistently.

References