Simple SlabApplication · Simple Slab Project
CVE-2020-35892
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 simple-slab crate before 0.3.3 for Rust. index() allows an out-of-bounds read.
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 confidenceThe simple-slab Rust crate (a memory allocator/data structure library) has an out-of-bounds read vulnerability in its index() function. This allows reading memory outside the allocated slab bounds, potentially exposing sensitive data or causing denial of service. The issue exists in versions before 0.3.3.
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
Simple SlabApplication
< 0.3.3CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the simple-slab dependency in your projectInspect your project's Cargo.toml file under [dependencies] and any Cargo.lock file for the simple-slab entryAffected if The simple-slab crate is listed as a direct or transitive dependency
-
Identify the installed version of simple-slabCheck the version number next to simple-slab in Cargo.lock, or run `cargo tree -p simple-slab` to see the resolved versionAffected if The version shown is below 0.3.3 (for example, 0.3.2, 0.3.1, 0.3.0, or any 0.x.y where x < 3)
-
Verify usage of the index() functionSearch your codebase for calls to slab.index() or use of the Slab struct's index methodAffected if Your code calls the index() function on a Slab instance
-
Confirm the vulnerability conditionIf simple-slab version is below 0.3.3 AND the index() function is called in your code, the out-of-bounds read can occurAffected if Both conditions are true: vulnerable version (< 0.3.3) AND index() function is invoked
You are affected if your project depends on simple-slab version less than 0.3.3 and your code uses the slab index() method.
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 · scoped0.3.3
Update the simple-slab crate to version 0.3.3 or later to obtain the patched version that adds proper bounds checking to the index() function.
simple-slab 0.3.3
- 1. Locate the Cargo.toml file in your project that declares simple-slab as a dependency
- 2. Find the current simple-slab version entry (e.g., simple-slab = "<0.3.3" or simple-slab = "0.X")
- 3. Update the version requirement to simple-slab = ">=0.3.3" or simply simple-slab = "0.3.3" to pin the minimum fixed version
- 4. Run 'cargo update simple-slab' to fetch the patched dependency version
- 5. Rebuild the project with 'cargo build' to incorporate the fixed crate
- 6. Run your test suite to verify the application functions correctly with the updated dependency
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Simple Slab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35892 — 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-35892 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