ArrApplication · Arr Project
CVE-2020-35887
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 · uneditedAn issue was discovered in the arr crate through 2020-08-25 for Rust. There is a buffer overflow in Index and IndexMut.
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 · moderate confidenceBuffer overflow vulnerability in the Rust arr crate's Index and IndexMut trait implementations, allowing out-of-bounds memory access through array indexing operations.
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
ArrApplication
<= 0.6.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.1/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.
-
Locate arr crate in dependenciesSearch your project for 'arr' in Cargo.toml and Cargo.lock files, or run 'cargo tree -p arr' if the crate is installed as a dependencyAffected if The arr crate appears as a direct or transitive dependency in your Rust project
-
Identify installed arr crate versionCheck Cargo.lock for the arr crate entry, or run 'cargo pkgid arr' to see the exact version numberAffected if The version listed is 0.6.0 or lower
-
Verify Index trait usageSearch source files for 'impl Index' patterns referencing arr types, or check if your code uses indexing syntax '[]' on arr typesAffected if Your code implements or uses the Index trait from the arr crate for custom array types
-
Confirm IndexMut trait implementationSearch source files for 'impl IndexMut' patterns referencing arr types, or look for mutable indexing assignments '[] =' on arr typesAffected if Your code implements or uses the IndexMut trait from the arr crate for custom array types
-
Test for out-of-bounds access possibilityReview all code paths where array indexing occurs with the arr crate's Index/IndexMut implementations, especially where index values are user-controlled or computedAffected if Any array index operation using arr's Index or IndexMut could potentially access memory outside array bounds
Your environment is affected if the arr crate version 0.6.0 or lower is present as a dependency and your code uses the Index or IndexMut trait implementations provided by arr for array access operations.
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.
From vendor dataUpdate to patched version of the arr crate if available; otherwise, verify all array index operations and consider alternative crates with similar functionality that have been security-audited.
Fix this in Arr
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35887 — 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-2020-35887 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