Several memory safety issues have been uncovered in an audit of rusqlite.
See https://github.com/rusqlite/rusqlite/releases/tag/0.23.0 for a complete list.
rga 0.5.9
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.
rga
(27 total, 12 outdated, 5 possibly insecure)
Crate | Required | Latest | Status |
---|---|---|---|
bincode | ^1.1.4 | 1.3.3 | up to date |
bzip2 ⚠️ | ^0.3.3 | 0.4.4 | out of date |
cachedir | ^0.1.1 | 0.3.1 | out of date |
chrono ⚠️ | ^0.4.6 | 0.4.37 | maybe insecure |
clap | ^2.33.0 | 4.5.4 | out of date |
crossbeam | ^0.7.1 | 0.8.4 | out of date |
encoding_rs | ^0.8.17 | 0.8.33 | up to date |
encoding_rs_io | ^0.1.6 | 0.1.7 | up to date |
env_logger | ^0.6.1 | 0.11.3 | out of date |
failure | ^0.1.5 | 0.1.8 | up to date |
flate2 | ^1.0.7 | 1.0.28 | up to date |
lazy_static | ^1.3.0 | 1.4.0 | up to date |
log | ^0.4.6 | 0.4.21 | up to date |
paste | ^0.1.5 | 1.0.14 | out of date |
path-clean | ^0.1.0 | 1.0.1 | out of date |
regex ⚠️ | ^1.1.6 | 1.10.4 | maybe insecure |
rkv | ^0.9.6 | 0.19.0 | out of date |
rusqlite ⚠️ | ^0.18.0 | 0.31.0 | out of date |
serde | ^1.0.92 | 1.0.197 | up to date |
serde_json | ^1.0.39 | 1.0.115 | up to date |
size_format | ^1.0.2 | 1.0.2 | up to date |
structopt | ^0.2.17 | 0.3.26 | out of date |
tar ⚠️ | ^0.4.26 | 0.4.40 | maybe insecure |
tree_magic_fork | ^0.2 | 0.2.2 | up to date |
xz2 | ^0.1.6 | 0.1.7 | up to date |
zip | ^0.5.2 | 0.6.6 | out of date |
zstd | ^0.4.24 | 0.13.1 | out of date |
rusqlite
: Various memory safety issuesSeveral memory safety issues have been uncovered in an audit of rusqlite.
See https://github.com/rusqlite/rusqlite/releases/tag/0.23.0 for a complete list.
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.
tar
: Links in archive can create arbitrary directoriesWhen unpacking a tarball that contains a symlink the tar
crate may create
directories outside of the directory it's supposed to unpack into.
The function errors when it's trying to create a file, but the folders are already created at this point.
use std::{io, io::Result};
use tar::{Archive, Builder, EntryType, Header};
fn main() -> Result<()> {
let mut buf = Vec::new();
{
let mut builder = Builder::new(&mut buf);
// symlink: parent -> ..
let mut header = Header::new_gnu();
header.set_path("symlink")?;
header.set_link_name("..")?;
header.set_entry_type(EntryType::Symlink);
header.set_size(0);
header.set_cksum();
builder.append(&header, io::empty())?;
// file: symlink/exploit/foo/bar
let mut header = Header::new_gnu();
header.set_path("symlink/exploit/foo/bar")?;
header.set_size(0);
header.set_cksum();
builder.append(&header, io::empty())?;
builder.finish()?;
};
Archive::new(&*buf).unpack("demo")
}
This has been fixed in https://github.com/alexcrichton/tar-rs/pull/259 and is
published as tar
0.4.36. Thanks to Martin Michaelis (@mgjm) for discovering
and reporting this, and Nikhil Benesch (@benesch) for the fix!
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.
bzip2
: bzip2 Denial of Service (DoS)Working with specific payloads can cause a Denial of Service (DoS) vector.
Both Decompress
and Compress
implementations can enter into infinite loops
given specific payloads entered that trigger it.
The issue is described in great detail in the bzip2 repository issue.
Thanks to bjrjk for finding and providing the patch for the issue and the maintainer responsibly responding to release a fix quickly.
Users who use the crate with untrusted data should update the bzip2
to 0.4.4.