CVE-2018-1000657 [High] | Memory Corruption in Rust

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.15%	0.54%	+0.39%
2	2026-01-05	0.14%	0.15%	+0.01%
3	2025-07-21	—	0.14%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.15%

0.54%

+0.39%

2026-01-05

0.14%

0.15%

+0.01%

2025-07-21

—

0.14%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.0	HIGH	`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]
4.6	2.0	MEDIUM	`AV:L/AC:L/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	3.9	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.0

HIGH

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

4.6

2.0

MEDIUM

AV:L/AC:L/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

3.9

6.4

[email protected]

OS Trackers for CVE-2018-1000657

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2018-1000657 not yet assigned priority: Debian including 1 source packages (rustc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2018-1000657
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2018-1000657
`suse`	high	CVE-2018-1000657 severity important: SUSE including 10 source package names (cargo, clippy, …), 10 product×package rows across 1 product lines (SUSE Linux Enterprise Module for Development Tools 15): Known Not Affected 10.	https://www.suse.com/security/cve/CVE-2018-1000657/
`ubuntu`	medium	CVE-2018-1000657 medium priority: Ubuntu including 1 source packages (rustc), 4 status rows across 4 suites (bionic, trusty, upstream, xenial): not-affected 3, released 1.	https://ubuntu.com/security/CVE-2018-1000657

Affected software / configurations for CVE-2018-1000657

Vendor	Product	Version	Raw CPE
rust-lang	rust	>= 1.3.0, < 1.22.0	cpe:2.3:a:rust-lang:rust::::::::

References for CVE-2018-1000657

URL	Tags
http://www.securityfocus.com/bid/105188	Third Party Advisory VDB Entry
https://github.com/rust-lang/rust/commit/f71b37bc28326e272a37b938e835d4f99113eec2	Patch Third Party Advisory
https://github.com/rust-lang/rust/issues/44800	Issue Tracking Third Party Advisory

URL

CVE-2018-1000657

Exploit prediction scoring system (EPSS) score for CVE-2018-1000657

Common vulnerability scoring system (CVSS) metrics for CVE-2018-1000657

Weakness enumeration for CVE-2018-1000657

OS Trackers for CVE-2018-1000657

Affected software / configurations for CVE-2018-1000657

References for CVE-2018-1000657