CVE-2020-36514

9.8 CRITICAL

📋 TL;DR

This vulnerability in the acc_reader Rust crate allows attackers to read from uninitialized memory locations via the fill_buf function. This can lead to information disclosure or potentially enable further exploitation. Any Rust application using vulnerable versions of the acc_reader crate is affected.

💻 Affected Systems

Products:
  • acc_reader Rust crate
Versions: All versions through 2020-12-27
Operating Systems: All platforms running Rust applications
Default Config Vulnerable: ⚠️ Yes
Notes: Any Rust application that imports and uses the vulnerable acc_reader crate versions.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Information disclosure of sensitive memory contents, potentially enabling further attacks like privilege escalation or remote code execution.

🟠

Likely Case

Application crashes or information leakage of random memory contents.

🟢

If Mitigated

Limited impact with proper memory isolation and sandboxing.

🌐 Internet-Facing: HIGH - If the vulnerable crate is used in web services or APIs, attackers could exploit it remotely.
🏢 Internal Only: MEDIUM - Internal applications could still be exploited by malicious insiders or compromised internal systems.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability is in a core library function, making exploitation relatively straightforward if the application uses the vulnerable code path.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Versions after 2020-12-27

Vendor Advisory: https://rustsec.org/advisories/RUSTSEC-2020-0155.html

Restart Required: Yes

Instructions:

1. Update Cargo.toml to use acc_reader version > 0.12.27
2. Run 'cargo update acc_reader'
3. Rebuild and redeploy your application
4. Restart affected services

🔧 Temporary Workarounds

Remove acc_reader dependency

all

Replace acc_reader with alternative safe crates or implement required functionality differently

cargo remove acc_reader

🧯 If You Can't Patch

  • Isolate affected applications in containers or VMs with limited permissions
  • Implement network segmentation to limit exposure of vulnerable services

🔍 How to Verify

Check if Vulnerable:

Check Cargo.lock for acc_reader version <= 0.12.27 or run 'cargo audit'

Check Version:

grep acc_reader Cargo.lock

Verify Fix Applied:

Verify Cargo.lock shows acc_reader version > 0.12.27 and 'cargo audit' reports no vulnerabilities

📡 Detection & Monitoring

Log Indicators:

  • Application crashes with memory access violations
  • Unexpected memory read errors

Network Indicators:

  • Unusual memory-related requests to services using acc_reader

SIEM Query:

process.name:your_app AND (event.code:ACCESS_VIOLATION OR error.message:*memory*)

🔗 References

📤 Share & Export