# CVE-2009-5152: Race condition in n/a

> Privileged local users can bypass Computrace Agent security controls by exploiting a race condition with the Dell Client Configuration Utility.

- **Severity:** Medium 4.1 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2018
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5hf6-7gxx-55wg

## What is CVE-2009-5152?

CVE-2009-5152 is a medium-severity vulnerability in n/a, published on 11 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Absolute Computrace Agent, as distributed on certain Dell Inspiron systems through 2009, has a race condition with the Dell Client Configuration Utility (DCCU), which allows privileged local users to change Computrace Agent's activation/deactivation status to the factory default via a crafted TaskResult.xml file.

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

## Which versions are affected by CVE-2009-5152?

It affects 1 product.


Products: Absolute Computrace Agent.

## How do I fix CVE-2009-5152?

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

## Is CVE-2009-5152 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-5150](https://insights.sbomify.com/CVE-2009-5150/): Security feature bypass in n/a (medium 6.7)
- [CVE-2009-5151](https://insights.sbomify.com/CVE-2009-5151/): Security feature bypass in n/a (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5152 and fix it if it is affected.

What it is: CVE-2009-5152 is a medium-severity vulnerability in n/a, published on 11 May 2018. 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-2009-5152 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-2009-5152/ (Markdown: https://insights.sbomify.com/CVE-2009-5152/index.md)
```

## Sources

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

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