# CVE-2010-5159: Race condition in n/a

> Local attackers can bypass kernel-mode security hooks via a race condition to execute blocked malicious code in Dr.Web Security Space.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2012
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-v3pw-85gv-xrjf

## What is CVE-2010-5159?

CVE-2010-5159 is a high-severity vulnerability in n/a, published on 25 Aug 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Race condition in Dr.Web Security Space Pro 6.0.0.03100 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

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2010-5159?

It affects 1 product.


Products: Drweb Web Security Space.

## How do I fix CVE-2010-5159?

No fix has been published for CVE-2010-5159 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-5159 being exploited?

There is no known exploitation of CVE-2010-5159 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-5159 and fix it if it is affected.

What it is: CVE-2010-5159 is a high-severity vulnerability in n/a, published on 25 Aug 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-5159 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-5159/ (Markdown: https://insights.sbomify.com/CVE-2010-5159/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-5159
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-5159
- OSV: https://osv.dev/vulnerability/CVE-2010-5159

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-5159/
Summaries are generated and may contain mistakes; the official description above is the record.