Deps.rs

tor-config 0.24.0

[![dependency status](https://deps.rs/crate/tor-config/0.24.0/status.svg)](https://deps.rs/crate/tor-config/0.24.0)

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 tor-config

Dependencies

(29 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 amplify^44.8.0up to date
 cfg-if^1.0.01.0.0up to date
 derive-deftly^0.140.14.2up to date
 derive_builder_fork_arti^0.11.20.11.2up to date
 directories^55.0.1up to date
 educe^0.4.60.6.0out of date
 either^11.13.0up to date
 figment^0.10.180.10.19up to date
 fs-mistrust^0.8.00.8.2up to date
 futures^0.3.140.3.31up to date
 itertools^0.13.00.13.0up to date
 notify^77.0.0up to date
 once_cell^11.20.2up to date
 paste^11.0.15up to date
 postage^0.5.00.5.0up to date
 regex ⚠️^11.11.1maybe insecure
 serde^1.0.1031.0.215up to date
 serde-value^0.7.00.7.0up to date
 serde_ignored^0.1.30.1.10up to date
 shellexpand^3.03.1.0up to date
 strum^0.26.30.26.3up to date
 thiserror^12.0.4out of date
 toml^0.8.80.8.19up to date
 tor-basic-utils^0.24.00.25.0out of date
 tor-config-path^0.24.00.25.0out of date
 tor-error^0.24.00.25.0out of date
 tor-rtcompat^0.24.00.25.0out of date
 tracing^0.1.360.1.41up to date
 void^11.0.2up to date

Dev dependencies

(8 total, 2 outdated)

CrateRequiredLatestStatus
 dirs^5.0.05.0.1up to date
 rmp-serde^11.3.0up to date
 serde_json^1.0.501.0.133up to date
 tempfile^33.14.0up to date
 test-temp-dir^0.3.00.3.0up to date
 tor-rtcompat^0.24.00.25.0out of date
 tor-rtmock^0.24.00.25.0out of date
 tracing-test^0.2.40.2.5up to date

Security Vulnerabilities

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.