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.
dinero-rs(15 total, 4 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| num | ^0.4.0 | 0.4.3 | up to date |
| glob | ^0.3.0 | 0.3.1 | up to date |
| colored | ^2.0.0 | 2.2.0 | up to date |
| chrono ⚠️ | ^0.4.19 | 0.4.39 | maybe insecure |
| regex ⚠️ | ^1 | 1.11.1 | maybe insecure |
| lazy_static | ^1.4.0 | 1.5.0 | up to date |
| structopt | ^0.3.21 | 0.3.26 | up to date |
| shellexpand | ^2.1.0 | 3.1.0 | out of date |
| two_timer | ^2.2.0 | 2.2.5 | up to date |
| terminal_size | ^0.1.16 | 0.4.1 | out of date |
| pest | ^2.0 | 2.7.15 | up to date |
| pest_derive | ^2.0 | 2.7.15 | up to date |
| rustyline | ^8.2.0 | 15.0.0 | out of date |
| shlex ⚠️ | ^1.0.0 | 1.3.0 | maybe insecure |
| prettytable-rs | ^0.8.0 | 0.10.0 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert_cmd | ^2.0.0 | 2.0.16 | up to 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.
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.
shlex: Multiple issues involving quote APIAffected versions of this crate allowed the bytes { and \xa0 to appear
unquoted and unescaped in command arguments.
If the output of quote or join is passed to a shell, then what should be a
single command argument could be interpreted as multiple arguments.
This does not directly allow arbitrary command execution (you can't inject a command substitution or similar). But depending on the command you're running, being able to inject multiple arguments where only one is expected could lead to undesired consequences, potentially including arbitrary command execution.
The flaw was corrected in version 1.2.1 by escaping additional characters. Updating to 1.3.0 is recommended, but 1.2.1 offers a more minimal fix if desired.
Workaround: Check for the bytes { and \xa0 in quote/join input or
output.
(Note: { is problematic because it is used for glob expansion. \xa0 is
problematic because it's treated as a word separator in specific
environments.)
Version 1.3.0 deprecates the quote and join APIs in favor of try_quote
and try_join, which behave the same except that they have Result return
type, returning Err if the input contains nul bytes.
Strings containing nul bytes generally cannot be used in Unix command arguments or environment variables, and most shells cannot handle nul bytes even internally. If you try to pass one anyway, then the results might be security-sensitive in uncommon scenarios. More details here.
Due to the low severity, the behavior of the original quote and join APIs
has not changed; they continue to allow nuls.
Workaround: Manually check for nul bytes in quote/join input or output.
The quote family of functions does not and cannot escape control characters.
With non-interactive shells this is perfectly safe, as control characters have
no special effect. But if you writing directly to the standard input of an
interactive shell (or through a pty), then control characters can cause
misbehavior including arbitrary command injection.
This is essentially unfixable, and has not been patched. But as of version 1.3.0, documentation has been added.
Future versions of shlex may add API variants that avoid the issue at the
cost of reduced portability.