CVE-2010-5178: n/a vulnerability

CVE-2010-5178: Race condition in ThreatFire 4.7.0.17 on Windows XP allows local users to bypass kernel-mode hook handlers,...

Race condition in ThreatFire 4.7.0.17 on Windows XP allows local users to bypass kernel-mode hook handlers, and execute dangerous code that would otherwise be blocked by a handler but not blocked by signature-based malware detection, via certain user-space memory changes during hook-handler execution, aka an argument-switch attack or a KHOBE attack. NOTE: this issue is disputed by some third parties because it is a flaw in a protection mechanism for situations where a crafted program has already begun to execute

UnknownCVSS not scoredNot KEV-listedUpdatedSep 17, 2024, 02:47 UTC (UTC+00:00)

Security readout for executives and security teams

This CVE describes a bypass of ThreatFire 4.7.0.17 on Windows XP. A local program already running on the machine could race ThreatFire's protection checks and execute code that behavior blocking might otherwise stop. The issue is old, platform-specific, and disputed as a protection-mechanism flaw rather than initial compromise. Exposure appears limited to Windows XP endpoints running ThreatFire 4.7.0.17. The bundle's affected-products metadata is nonspecific, so inventory confirmation is required. Modern environments without this legacy product and OS combination are unlikely to be directly exposed. Prioritize as a legacy-risk cleanup item, not an emergency internet-wide exposure. If Windows XP and ThreatFire 4.7.0.17 are still present, remove or isolate them because the control may be bypassed after malware starts running. Mitigation focus: Identify any Windows XP systems still running ThreatFire 4.7.0.17.; Check vendor or successor-product guidance for supported upgrades or removal paths.; Retire unsupported Windows XP endpoints where business constraints allow..

Prepared: Jun 28, 2026, 00:52 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.

cve · low confidence lookup

CVE-2010-5178 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: Aug 25, 2012, 21: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

1Source 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

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.