RustApplication · Rust Lang
CVE-2018-1000810
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Rust Programming Language Standard Library version 1.29.0, 1.28.0, 1.27.2, 1.27.1, 127.0, 126.2, 126.1, 126.0 contains a CWE-680: Integer Overflow to Buffer Overflow vulnerability in standard library that can result in buffer overflow. This attack appear to be exploitable via str::repeat, passed a large number, can overflow an internal buffer. This vulnerability appears to have been fixed in 1.29.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA buffer overflow vulnerability exists in the Rust Standard Library's str::repeat function. When a large numeric argument is passed to repeat(), an integer overflow occurs in internal buffer size calculation, causing allocated buffer to be undersized and leading to buffer overflow. This is exploitable via crafted input to any code using str::repeat.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
RustApplication
= 1.26.0= 1.26.1= 1.26.2= 1.27.0= 1.27.1= 1.27.2= 1.28.0= 1.29.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Rust toolchain versionRun `rustc --version` or `rustc --version && rustup show` to identify the exact Rust compiler versionAffected if Version is 1.26.0, 1.26.1, 1.26.2, 1.27.0, 1.27.1, 1.27.2, 1.28.0, or 1.29.0 (versions before the 1.29.1 patch)
-
Identify use of str::repeat in codebaseSearch source code for occurrences of `.repeat(` method calls on string literals or str variables, using grep or IDE search across project source filesAffected if Codebase contains any call to the repeat() method on str or String types
-
Determine if repeat() receives large or user-controlled numeric argumentsReview all identified repeat() call sites to see if the numeric argument (the repetition count) could be large (e.g., from user input, config files, or calculated from unchecked arithmetic)Affected if The repetition count passed to repeat() can exceed a safe threshold or originate from untrusted input without bounds checking
You are affected if your Rust toolchain version is between 1.26.0 and 1.29.0 inclusive AND your code uses str::repeat() with a potentially large repetition count from any source.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Rust toolchain to version 1.29.1 or later to obtain the patched standard library. Audit existing code that uses str::repeat to ensure no exploitation has occurred.
1.29.1 or later
- Upgrade Rust to version 1.29.1 or later using rustup: rustup update stable
- Alternatively, verify current version with: rustc --version
- If using a specific toolchain, update with: rustup update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rust
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data