CVE-2011-0036: n/a vulnerability

CVE-2011-0036: Microsoft Internet Explorer 6, 7, and 8 does not properly handle objects in memory, which allows remote att...

Microsoft Internet Explorer 6, 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 memory corruption, related to a "dangling pointer," aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2010-2556 and CVE-2011-0035.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 21:43 UTC (UTC+00:00)

Security readout for executives and security teams

This is an old Internet Explorer memory-safety flaw that could let a remote attacker run code if a user encountered malicious web content. Business risk is concentrated in legacy environments still running Internet Explorer 6, 7, or 8, or systems that depend on those browser components. Likely exposure is limited to legacy Windows environments where Internet Explorer 6, 7, or 8 remains installed or usable. The bundle does not identify affected non-Microsoft products, despite third-party advisory references. Prioritize remediation if any legacy browser estate remains. For modern environments without Internet Explorer 6-8, urgency is lower, but confirm there are no hidden dependencies in kiosks, industrial, or legacy business systems. Mitigation focus: Apply Microsoft MS11-003 or the applicable supported Internet Explorer cumulative security update.; Remove or retire Internet Explorer 6, 7, and 8 where operationally possible.; Restrict legacy browser use to isolated, business-critical workflows only..

Prepared: Jun 27, 2026, 18:32 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2011-0036 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Feb 10, 2011, 15:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
oval:org.mitre.oval:def:12261CVE reference · vdb-entry, signature
MS11-003CVE reference · vendor-advisory, x_refsource_MS
ms-explorer-code-exec(64912)CVE reference · vdb-entry, x_refsource_XF

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.