# CVE-2018-25008: Race condition in n/a

> Weak synchronization in Rust's Arc::get_mut allows race conditions leading to memory safety issues, potentially enabling code execution or crashes.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Apr 2021
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-25008, GHSA-prm6-42x6-pwfm

## What is CVE-2018-25008?

CVE-2018-25008 is a medium-severity vulnerability in n/a, published on 14 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the standard library in Rust before 1.29.0, there is weak synchronization in the Arc::get_mut method. This synchronization issue can be lead to memory safety issues through race conditions.

Weakness: CWE-662 (Improper Synchronization)

## Which versions are affected by CVE-2018-25008?

It affects 1 product.


Products: Rust-Lang Rust.

## How do I fix CVE-2018-25008?

Upgrade to a fixed version.

## Is CVE-2018-25008 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36318](https://insights.sbomify.com/CVE-2020-36318/): Use after free in n/a (critical 9.8)
- [CVE-2018-1000810](https://insights.sbomify.com/CVE-2018-1000810/): Integer overflow in n/a (critical 9.8)
- [CVE-2021-29922](https://insights.sbomify.com/CVE-2021-29922/): Security feature bypass in n/a (critical 9.1)
- [CVE-2024-43402](https://insights.sbomify.com/CVE-2024-43402/): Rust OS Command Injection/Argument Injection vulnerability (high 8.2)
- [CVE-2018-1000657](https://insights.sbomify.com/CVE-2018-1000657/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25008 and fix it if it is affected.

What it is: CVE-2018-25008 is a medium-severity vulnerability in n/a, published on 14 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-25008 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-2018-25008/ (Markdown: https://insights.sbomify.com/CVE-2018-25008/index.md)
```

## Sources

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

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