This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate rustdesk

Dependencies

(29 total, 5 outdated)

CrateRequiredLatestStatus
 whoami^1.21.3.0up to date
 serde_derive^1.01.0.152up to date
 serde^1.01.0.152up to date
 serde_json^1.01.0.91up to date
 cfg-if^1.01.0.0up to date
 lazy_static^1.41.4.0up to date
 sha2^0.100.10.6up to date
 repng^0.20.2.2up to date
 libc^0.20.2.139up to date
 flexi_logger^0.220.24.2out of date
 runas^0.20.2.1up to date
 dasp^0.110.11.0up to date
 rubato^0.120.12.0up to date
 samplerate^0.20.2.4up to date
 async-trait^0.10.1.64up to date
 uuid^1.01.3.0up to date
 clap^3.04.1.4out of date
 rpassword^7.07.2.0up to date
 base64^0.130.21.0out of date
 sysinfo^0.240.27.7out of date
 num_cpus^1.131.15.0up to date
 bytes^1.21.4.0up to date
 wol-rs^0.9.11.0.0out of date
 flutter_rust_bridge^1.61.11.62.0up to date
 errno^0.2.80.2.8up to date
 url^2.12.3.1up to date
 reqwest^0.110.11.14up to date
 chrono^0.4.230.4.23up to date
 cidr-utils^0.5.90.5.10up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 hound^3.53.5.0up to date

Build dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 cc^1.01.0.79up to date
 flutter_rust_bridge_codegen^1.61.11.62.0up to date

Crate scrap

Dependencies

(7 total, all up-to-date)

CrateRequiredLatestStatus
 block^0.10.1.6up to date
 cfg-if^1.01.0.0up to date
 libc^0.20.2.139up to date
 num_cpus^1.131.15.0up to date
 lazy_static^1.41.4.0up to date
 webm^1.01.0.2up to date
 winapi^0.30.3.9up to date

Build dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 target_build_utils^0.30.3.1up to date
 bindgen^0.590.63.0out of date

Crate hbb_common

Dependencies

(22 total, 4 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 protobuf^3.13.2.0up to date
 tokio ⚠️^1.201.25.0maybe insecure
 tokio-util^0.70.7.4up to date
 futures^0.30.3.26up to date
 bytes^1.21.4.0up to date
 log^0.40.4.17up to date
 env_logger^0.90.10.0out of date
 socket2^0.30.4.7out of date
 zstd^0.90.12.3+zstd.1.5.2out of date
 quinn^0.80.9.3out of date
 anyhow^1.01.0.68up to date
 futures-util^0.30.3.26up to date
 directories-next^2.02.0.0up to date
 rand^0.80.8.5up to date
 serde_derive^1.01.0.152up to date
 serde^1.01.0.152up to date
 lazy_static^1.41.4.0up to date
 dirs-next^2.02.0.0up to date
 filetime^0.20.2.19up to date
 sodiumoxide^0.20.2.7up to date
 regex ⚠️^1.41.7.1maybe insecure
 chrono ⚠️^0.40.4.23maybe insecure

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 toml^0.50.7.1out of date
 serde_json^1.01.0.91up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 protobuf-codegen^3.13.2.0up to date

Crate simple_rc

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 serde_derive^1.01.0.152up to date
 serde^1.01.0.152up to date
 walkdir^22.3.2up to date

Crate enigo

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 serde^1.01.0.152up to date
 serde_derive^1.01.0.152up to date
 log^0.40.4.17up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 pkg-config^0.30.3.26up to date

Crate clipboard

Dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 thiserror^1.0.301.0.38up to date
 lazy_static^1.41.4.0up to date
 serde^1.01.0.152up to date
 serde_derive^1.01.0.152up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 cc^1.01.0.79up to date

Crate virtual_display

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 lazy_static^1.41.4.0up to date
 libloading^0.70.7.4up to date

Crate dylib_virtual_display

Dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 thiserror^1.0.301.0.38up to date
 lazy_static^1.41.4.0up to date
 serde^1.01.0.152up to date
 serde_derive^1.01.0.152up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 cc^1.01.0.79up to date

Crate rustdesk-portable-packer

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 brotli^3.3.43.3.4up to date
 dirs^4.0.04.0.0up to date
 md5^0.7.00.7.0up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 embed-resource^1.71.8.0up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

regex: Regexes with large repetitions on empty sub-expressions take a very long time to parse

RUSTSEC-2022-0013

The 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.

Overview

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.

Affected versions

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.

Mitigations

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.

Acknowledgements

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.

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overriden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);