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 cracktunes

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 config-file^0.20.2.3up to date
 dotenvy^0.150.15.7up to date
 tracing-subscriber^0.30.3.19up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 vergen-gitcl^1.0.11.0.5up to date

Crate crack-core

Dependencies

(31 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 cfg-if^11.0.0up to date
 dashmap^66.1.0up to date
 rustls ⚠️^0.230.23.23maybe insecure
 audiopus^0.3.0-rc.00.2.0up to date
 async-trait^0.10.1.87up to date
 anyhow^1.01.0.97up to date
 bytes^1.71.10.1up to date
 colored^2.13.0.0out of date
 const-random^0.10.1.18up to date
 chrono ⚠️^0.40.4.40maybe insecure
 lazy_static^1.51.5.0up to date
 rand^0.80.9.0out of date
 regex^1.111.11.1up to date
 serde^1.01.0.219up to date
 serde_derive^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 url^2.52.5.4up to date
 sys-info^0.90.9.1up to date
 prometheus^0.130.13.4up to date
 typemap_rev^0.30.3.0up to date
 either^1.131.15.0up to date
 once_cell^1.201.21.0up to date
 strsim^0.110.11.1up to date
 itertools^0.130.14.0out of date
 indexmap^2.22.8.0up to date
 futures^0.30.3.31up to date
 urlencoding^2.12.1.3up to date
 extract_map^0.10.2.0out of date
 rusty_ytdl^0.7.40.7.4up to date
 serenity-voice-model^0.20.2.0up to date
 rspotify^0.130.14.0out of date

Dev dependencies

(4 total, 3 outdated)

CrateRequiredLatestStatus
 ctor^0.20.4.1out of date
 tungstenite^0.24.00.26.2out of date
 async-tungstenite^0.28.00.29.1out of date
 sqlx^0.8.20.8.3up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 vergen-gitcl^1.0.11.0.5up to date

Crate crack-osint

Dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 whois-rust^1.61.6.0up to date
 sha1^0.100.10.6up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date

Crate crack-gpt

Dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 backoff^0.4.1-alpha.10.4.0out of date
 async-openai^0.26.00.28.0out of date
 ttl_cache^0.50.5.1up to date
 const_format^0.20.2.34up to date

Crate crack-bf

No external dependencies! 🙌

Crate crack-voting

Dependencies

(6 total, 2 possibly insecure)

CrateRequiredLatestStatus
 lazy_static^1.51.5.0up to date
 dbl-rs^0.40.4.0up to date
 warp ⚠️^0.30.3.7maybe insecure
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 chrono ⚠️^0.40.4.40maybe insecure

Crate crack-testing

Dependencies

(12 total, 3 outdated)

CrateRequiredLatestStatus
 anyhow^1.01.0.97up to date
 clap^4.54.5.32up to date
 dashmap^6.16.1.0up to date
 once_cell^1.201.21.0up to date
 futures^0.30.3.31up to date
 rand^0.80.9.0out of date
 reqwest^0.12.90.12.12up to date
 tracing^0.1.400.1.41up to date
 thiserror^1.0.692.0.12out of date
 url^2.52.5.4up to date
 rusty_ytdl^0.7.40.7.4up to date
 rspotify^0.130.14.0out of date

Crate crack-types

Dependencies

(7 total, 2 outdated)

CrateRequiredLatestStatus
 typemap_rev^0.3.00.3.0up to date
 reqwest^0.12.90.12.12up to date
 url^2.52.5.4up to date
 thiserror^1.0.692.0.12out of date
 humantime^2.12.1.0up to date
 rspotify^0.130.14.0out of date
 rusty_ytdl^0.7.40.7.4up 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

warp: Improper validation of Windows paths could lead to directory traversal attack

RUSTSEC-2022-0082

Path resolution in warp::filters::fs::dir didn't correctly validate Windows paths meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed and respond with the contents of c:/windows/web/screen/img101.png. Thus users could potentially read files anywhere on the filesystem.

This only impacts Windows. Linux and other unix likes are not impacted by this.

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.