Memory Corruption Affecting signal-simple package, versions *


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
0.34% (56th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Memory Corruption vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RUST-SIGNALSIMPLE-1316321
  • published9 Jul 2021
  • disclosed15 Nov 2020
  • creditUnknown

Introduced: 15 Nov 2020

CVE-2020-36446  (opens in a new tab)
CWE-119  (opens in a new tab)

How to fix?

There is no fixed version for signal-simple.

Overview

signal-simple is a Library to handle and send system signals.

Affected versions of this package are vulnerable to Memory Corruption. Affected versions of this crate unconditionally implement Send/Sync for SyncChannel<T>. SyncChannel<T> doesn't provide access to &T but merely serves as a channel that consumes and returns owned T. Users can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs. Using T = Arc<Cell<_> allows to create data races (which can lead to memory corruption), and using T = MutexGuard<T> allows to unlock a mutex from a thread that didn't lock the mutex.

CVSS Base Scores

version 3.1