CVE-2020-35898

9.1 CRITICAL

📋 TL;DR

This vulnerability in the actix-utils Rust crate allows obtaining multiple mutable references to the same data, violating Rust's memory safety guarantees. This can lead to use-after-free, data races, or other memory corruption issues. Any Rust application using actix-utils versions before 2.0.0 is affected.

💻 Affected Systems

Products:
  • actix-utils Rust crate
Versions: All versions before 2.0.0
Operating Systems: All operating systems running Rust applications
Default Config Vulnerable: ⚠️ Yes
Notes: Any Rust application that depends on actix-utils <2.0.0 is vulnerable regardless of configuration

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise, data exfiltration, or service disruption

🟠

Likely Case

Application crashes, memory corruption, or denial of service due to undefined behavior

🟢

If Mitigated

Limited impact if application runs with minimal privileges and proper sandboxing

🌐 Internet-Facing: HIGH - Web applications using actix-web framework could be remotely exploitable
🏢 Internal Only: MEDIUM - Internal services could be compromised leading to lateral movement

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability is in a fundamental memory safety primitive, making exploitation relatively straightforward for attackers familiar with Rust memory corruption

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.0.0

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

Restart Required: Yes

Instructions:

1. Update Cargo.toml to require actix-utils >=2.0.0
2. Run 'cargo update' to fetch the patched version
3. Rebuild and redeploy your application

🔧 Temporary Workarounds

Pin to safe version

all

Force Cargo to use the patched version by specifying exact version in Cargo.toml

actix-utils = "2.0.0"

🧯 If You Can't Patch

  • Isolate affected applications in network segments with strict egress filtering
  • Implement runtime monitoring for memory corruption patterns and crash detection

🔍 How to Verify

Check if Vulnerable:

Check Cargo.lock or run 'cargo tree | grep actix-utils' to see if version <2.0.0 is present

Check Version:

grep actix-utils Cargo.lock

Verify Fix Applied:

Run 'cargo update' and verify actix-utils >=2.0.0 appears in Cargo.lock

📡 Detection & Monitoring

Log Indicators:

  • Application crashes with segmentation faults
  • Memory corruption errors in Rust panic messages

Network Indicators:

  • Unusual outbound connections from Rust application processes

SIEM Query:

process.name:"your_rust_app" AND (event.type:"crash" OR event.type:"segfault")

🔗 References

📤 Share & Export