CVE-2010-5155: Race Condition
First published: Sat Aug 25 2012(Updated: )
** DISPUTED ** Race condition in Blink Professional 4.6.1 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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Eeye Blink | =4.6.1 | |
| Microsoft Windows XP | ||
| All of | ||
| Eeye Blink | =4.6.1 | |
| Microsoft Windows XP |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.securityfocus.com/bid/39924
- http://www.theregister.co.uk/2010/05/07/argument_switch_av_bypass/
- http://www.osvdb.org/67660
- http://archives.neohapsis.com/archives/bugtraq/2010-05/0026.html
- http://www.f-secure.com/weblog/archives/00001949.html
- http://matousec.com/info/advisories/khobe-8.0-earthquake-for-windows-desktop-security-software.php
- http://countermeasures.trendmicro.eu/you-just-cant-trust-a-drunk/
- http://matousec.com/info/articles/khobe-8.0-earthquake-for-windows-desktop-security-software.php
- http://archives.neohapsis.com/archives/fulldisclosure/2010-05/0066.html
Frequently Asked Questions
What is the severity of CVE-2010-5155?
CVE-2010-5155 is classified as a high-severity vulnerability due to its potential to allow local users to execute arbitrary code.
How does CVE-2010-5155 exploit a race condition?
CVE-2010-5155 exploits a race condition in the Blink Professional 4.6.1 software, enabling bypass of kernel-mode hook handlers.
What systems are affected by CVE-2010-5155?
CVE-2010-5155 affects the Eeye Blink Professional 4.6.1 running on Windows XP.
How do I mitigate CVE-2010-5155?
To mitigate CVE-2010-5155, ensure that you do not use vulnerable versions of Blink Professional or consider upgrading to a patched version if available.
Are there any known workarounds for CVE-2010-5155?
There are no widely recognized workarounds for CVE-2010-5155; upgrading the affected software is recommended.
- collector/nvd-historical
- agent/type
- agent/first-publish-date
- agent/references
- agent/severity
- agent/weakness
- agent/status
- agent/description
- agent/softwarecombine
- agent/event
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/author
- vendor/eeye
- canonical/eeye blink
- version/eeye blink/4.6.1
- vendor/microsoft
- canonical/microsoft windows xp
- status/disputed