# CVE-2018-1000657: Memory corruption in n/a

> A buffer overflow in the Rust standard library's VecDeque reserve function allows arbitrary code execution, requiring an upgrade to a patched version.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/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:** Yes
- **Published:** 20 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1000657, GHSA-7877-m5c6-fgmx

## What is CVE-2018-1000657?

CVE-2018-1000657 is a high-severity memory corruption vulnerability in n/a, published on 20 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Rust Programming Language Rust standard library version Commit bfa0e1f58acf1c28d500c34ed258f09ae021893e and later; stable release 1.3.0 and later contains a Buffer Overflow vulnerability in std::collections::vec_deque::VecDeque::reserve() function that can result in Arbitrary code execution, but no proof-of-concept exploit is currently published.. This vulnerability appears to have been fixed in after commit fdfafb510b1a38f727e920dccbeeb638d39a8e60; stable release 1.22.0 and later.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Rust-Lang Rust.

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

Upgrade to a fixed version.

## Is CVE-2018-1000657 being exploited?

There is no known exploitation of CVE-2018-1000657 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-1000622](https://insights.sbomify.com/CVE-2018-1000622/): Other in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000657 is a high-severity memory corruption vulnerability in n/a, published on 20 Aug 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-2018-1000657 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-1000657/ (Markdown: https://insights.sbomify.com/CVE-2018-1000657/index.md)
```

## Sources

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

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