SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2006-2492Public Intelligence Dossier
Source: microsoft · Limited verification•Last verified: •Collection Degraded
CVE-2006-2492ListedHIGH (raw)CVSS 8.8CWE-120

Buffer overflow in Microsoft Word in Office 2000 SP3, Office XP SP3, Office 2003 Sp1 and SP2, and Microsoft Works Suites through 2006, allows user-assisted attackers to execute arbitrary code via a malformed object pointer, as originally reported by ISC on 20060519 for a zero-day attack.

Published: 20 May 2006•Last updated: 17 Jun 2026, 03:55 AM IST•Source identifier: cret@cert.org
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added08 Jun 2022
Due22 Jun 2022
RansomwareUnknown
CVSS score
8.8HIGH (raw)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Metric sourcenvd@nist.gov
EPSS probability
48.1%0.481
Percentile99th
Weakness type
CWE-120
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

Buffer overflow in Microsoft Word in Office 2000 SP3, Office XP SP3, Office 2003 Sp1 and SP2, and Microsoft Works Suites through 2006, allows user-assisted attackers to execute arbitrary code via a malformed object pointer, as originally reported by ISC on 20060519 for a zero-day attack.

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; Microsoft or Microsoft-managed product relevance; HIGH severity; Source-confirmed exploitation or CISA KEV/ransomware metadata

Affected Products & Remediation

2 source-backed products
Affected products and versions (source)
  • microsoft office · 2000; 2003; xp · NVD CPE · Source
  • microsoft works suite · >= 2000 <= 2006 · NVD CPE · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply updates per vendor instructions.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: Apply updates per vendor instructions.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); user-interaction-client (CVSS AV:N, CVSS UI:R)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Identify endpoints reporting this CVE, especially those used for email and web browsing.Telemetry: DeviceTvmSoftwareVulnerabilities · A network vector that needs user interaction points at user-facing client software. · Rule user-interaction-client

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review unusual child processes started by the affected client application on affected endpoints.Telemetry: DeviceProcessEvents · Hunting hypothesis from the CVSS vector; it does not show that exploitation occurred. · Rule user-interaction-client

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
08 Jun 2022
Required action due
22 Jun 2022
Known ransomware use
Unknown

Apply updates per vendor instructions.

Change History & Source Data

— No recorded material change

CNA / source
cret@cert.org
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:a:microsoft:office:2000:sp3:*:*:*:*:*:*, cpe:2.3:a:microsoft:office:2003:sp1:*:*:*:*:*:*, cpe:2.3:a:microsoft:office:2003:sp2:*:*:*:*:*:*, cpe:2.3:a:microsoft:office:xp:sp3:*:*:*:*:*:*, cpe:2.3:a:microsoft:works_suite:*:*:*:*:*:*:*:*

Evidence & Provenance

4 public sources
CISA KEV CatalogAdded 2022-06-08nvd.nist.govSource recorddocs.microsoft.comSource recordexchange.xforce.ibmcloud.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2006-2492
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2006-2492
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2006-2492"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.