Acc ReaderApplication · Acc Reader Project
CVE-2020-36513
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. read_up_to 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 has a memory safety vulnerability in the read_up_to function, which may read from uninitialized memory locations. This can lead to information disclosure of sensitive data from memory or undefined behavior, which could potentially be exploited for more severe attacks.
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 the acc_reader crate in your project dependenciesSearch your project's Cargo.toml and Cargo.lock files for 'acc_reader' or 'acc_reader' crate referencesAffected if The crate is listed as a dependency in your project
-
Identify the installed version of acc_readerCheck the version number specified next to acc_reader in Cargo.lock, or run 'cargo tree -p acc_reader' to see the exact versionAffected if The version is 2.0.0 or lower (any version <= 2.0.0)
-
Determine if read_up_to function is called in your codeSearch your codebase for any invocations of read_up_to function, typically in the pattern acc_reader::read_up_to or similar module-qualified callsAffected if Your code calls the read_up_to function from the acc_reader crate
-
Check if buffers passed to read_up_to may be uninitializedReview all call sites where read_up_to is used and inspect whether the buffer parameter is initialized (filled with values) before being passed to the functionAffected if Buffers passed to read_up_to are not initialized with a defined value before the call
Your environment is affected if the acc_reader crate version is 2.0.0 or lower AND your code uses the read_up_to function with potentially uninitialized buffers
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 a patched version of the acc_reader crate if available; otherwise, review and ensure any buffers passed to read_up_to are properly initialized before use.
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-36513 — 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-36513 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