Acc ReaderApplication · Acc Reader Project
CVE-2020-36514
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 acc_reader crate through 2020-12-27 for Rust. fill_buf may read from uninitialized memory locations.
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 confidenceThe acc_reader Rust crate contains a memory safety vulnerability where the fill_buf function may read from uninitialized memory locations. This can lead to information disclosure of potentially sensitive data remaining in memory, as well as undefined behavior.
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
Acc ReaderApplication
<= 2.0.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 acc_reader crate in dependenciesSearch your Cargo.toml, Cargo.lock, or dependency list for the acc_reader crate. Run 'cargo tree' or grep for 'acc_reader' in your project files.Affected if The acc_reader crate appears in your dependencies with version 2.0.0 or lower
-
Identify installed versionCheck Cargo.lock for the exact version number of acc_reader, or run 'cargo pkgid acc_reader' to see the installed version.Affected if The installed version is 2.0.0 or any version <= 2.0.0
-
Verify fill_buf function usageSearch your codebase for calls to fill_buf method on types from the acc_reader crate. Check source files for patterns like 'reader.fill_buf()' or similar.Affected if Your code calls the fill_buf function from acc_reader crate
-
Check for dependent crates using acc_readerRun 'cargo tree -i acc_reader' to see which of your dependencies transitively depend on acc_reader and may be affected.Affected if Any direct or transitive dependency uses a vulnerable version of acc_reader
You are affected if your project depends on acc_reader version 2.0.0 or lower and actively uses the fill_buf function or any code path that invokes it.
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 · scopedUpdate to a patched version of the acc_reader crate when available. Until then, avoid using the affected version in production or security-sensitive contexts, as uninitialized memory may contain sensitive data.
acc_reader version 2.0.1
- Update Cargo.toml to specify acc_reader version 2.0.1 or later
- Run cargo update acc_reader to update the dependency
- Run cargo build or cargo test to verify the update compiles correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Acc Reader
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-36514 — 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-36514 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