This project contains known security vulnerabilities. Find detailed information at the bottom.
barium-client(24 total, 12 outdated, 1 insecure, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base-62 | ^0.1 | 0.1.1 | up to date |
| rand | ^0.7 | 0.9.1 | out of date |
| rsa ⚠️ | ^0.3 | 0.9.8 | insecure |
| serde | ^1.0 | 1.0.219 | up to date |
| serde_json | ^1.0 | 1.0.140 | up to date |
| dirs | ^2.0 | 6.0.0 | out of date |
| gtk | ^0.8 | 0.18.2 | out of date |
| gtk_resources | ^0.1.5 | N/A | up to date |
| gdk | ^0.12 | 0.18.2 | out of date |
| gio | ^0.8 | 0.21.0 | out of date |
| glib | ^0.9 | 0.21.0 | out of date |
| pango | ^0.8 | 0.21.0 | out of date |
| padlock | ^0.2 | 0.2.0 | up to date |
| rmp-serde | ^0.14 | 1.3.0 | out of date |
| native-tls | ^0.2 | 0.2.14 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.73 | maybe insecure |
| tray-item | ^0.4.0-alpha | 0.10.0 | out of date |
| lazy_static | ^1.4 | 1.5.0 | up to date |
| trust-dns-client | ^0.19 | 0.23.2 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| log | ^0.4 | 0.4.27 | up to date |
| fern | ^0.6 | 0.7.1 | out of date |
| clipboard | ^0.5.0 | 0.5.0 | up to date |
| regex ⚠️ | ^1 | 1.11.1 | maybe insecure |
(2 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| regex ⚠️ | ^1.3 | 1.11.1 | maybe insecure |
| last-git-commit | ^0.2 | 0.2.0 | up to date |
barium-server(16 total, 4 outdated, 1 insecure, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| serde | ^1.0 | 1.0.219 | up to date |
| serde_json | ^1.0 | 1.0.140 | up to date |
| tokio ⚠️ | ^0.2 | 1.46.1 | out of date |
| padlock | ^0.2 | 0.2.0 | up to date |
| rmp-serde | ^0.14 | 1.3.0 | out of date |
| log | ^0.4 | 0.4.27 | up to date |
| fern | ^0.6 | 0.7.1 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| rsa ⚠️ | ^0.3 | 0.9.8 | insecure |
| lazy_static | ^1.4 | 1.5.0 | up to date |
| native-tls | ^0.2 | 0.2.14 | up to date |
| ipnet | ^2.3 | 2.11.0 | up to date |
| either | ^1.5 | 1.15.0 | up to date |
| iron | ^0.6 | 0.6.1 | up to date |
| router | ^0.6 | 0.6.0 | up to date |
| base-62 | ^0.1 | 0.1.1 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| last-git-commit | ^0.2 | 0.2.0 | up to date |
barium-shared(3 total, 2 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| serde | ^1.0 | 1.0.219 | up to date |
| rsa ⚠️ | ^0.3 | 0.9.8 | insecure |
| sha3 | ^0.9 | 0.10.8 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
tokio: Data race when sending and receiving after closing a `oneshot` channelIf a tokio::sync::oneshot channel is closed (via the
oneshot::Receiver::close method), a data race may occur if the
oneshot::Sender::send method is called while the corresponding
oneshot::Receiver is awaited or calling try_recv.
When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.
Note that the race only occurs when both halves of the channel are used
after the Receiver half has called close. Code where close is not used, or where the
Receiver is not awaited and try_recv is not called after calling close,
is not affected.
See tokio#4225 for more details.
regex: Regexes with large repetitions on empty sub-expressions take a very long time to parseThe Rust Security Response WG was notified that the regex crate did not
properly limit the complexity of the regular expressions (regex) it parses. An
attacker could use this security issue to perform a denial of service, by
sending a specially crafted regex to a service accepting untrusted regexes. No
known vulnerability is present when parsing untrusted input with trusted
regexes.
This issue has been assigned CVE-2022-24713. The severity of this vulnerability
is "high" when the regex crate is used to parse untrusted regexes. Other uses
of the regex crate are not affected by this vulnerability.
The regex crate features built-in mitigations to prevent denial of service
attacks caused by untrusted regexes, or untrusted input matched by trusted
regexes. Those (tunable) mitigations already provide sane defaults to prevent
attacks. This guarantee is documented and it's considered part of the crate's
API.
Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.
All versions of the regex crate before or equal to 1.5.4 are affected by this
issue. The fix is include starting from regex 1.5.5.
We recommend everyone accepting user-controlled regexes to upgrade immediately
to the latest version of the regex crate.
Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.
We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.
We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.
rsa: Marvin Attack: potential key recovery through timing sidechannelsDue to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.
No patch is yet available, however work is underway to migrate to a fully constant-time implementation.
The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.
This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.