# CVE-2005-1125: Race condition in n/a

> Attackers can bypass libsafe protection in multi-threaded applications via a race condition, enabling exploitation of other vulnerabilities.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7x55-jrxh-rmp2

## What is CVE-2005-1125?

CVE-2005-1125 is a medium-severity vulnerability in n/a, published on 16 Apr 2005. 

### Official description

Race condition in libsafe 2.0.16 and earlier, when running in multi-threaded applications, allows attackers to bypass libsafe protection and exploit other vulnerabilities before the _libsafe_die function call is completed.

## Which versions are affected by CVE-2005-1125?

It affects 1 product.


Products: Avaya Libsafe.

## How do I fix CVE-2005-1125?

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

## Is CVE-2005-1125 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1125 exists.

Public exploit code:

- Libsafe - Safety Check Bypass Vulnerability (Proof of Concept Exploit & Time Randomization to Thwart It) (github_poc): https://github.com/tagatac/libsafe-CVE-2005-1125
- Libsafe 2.0 - Multi-threaded Process Race Condition Security Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-0175](https://insights.sbomify.com/CVE-2002-0175/): Security feature bypass in n/a (medium 4.6)
- [CVE-2002-0176](https://insights.sbomify.com/CVE-2002-0176/): Other in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1125 and fix it if it is affected.

What it is: CVE-2005-1125 is a medium-severity vulnerability in n/a, published on 16 Apr 2005. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1125 exists.

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-2005-1125/ (Markdown: https://insights.sbomify.com/CVE-2005-1125/index.md)
```

## Sources

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

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