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 raider-server

Dependencies

(27 total, 14 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 log^0.30.4.20out of date
 clap^2.294.5.1out of date
 lazy_static^1.31.4.0up to date
 sha2^0.70.10.8out of date
 time ⚠️^0.10.3.34out of date
 rand^0.40.8.5out of date
 serde^1.01.0.197up to date
 serde_derive^1.01.0.197up to date
 toml^0.40.8.10out of date
 base64^0.60.21.7out of date
 validate^0.60.6.1up to date
 url_serde^0.20.2.0up to date
 chrono ⚠️^0.40.4.34maybe insecure
 native-tls^0.20.2.11up to date
 openssl-probe^0.10.1.5up to date
 lettre ⚠️^0.90.11.4out of date
 lettre_email^0.90.9.4up to date
 rocket^0.40.5.0out of date
 rocket_contrib^0.40.4.11up to date
 diesel ⚠️^1.12.1.4out of date
 r2d2^0.80.8.10up to date
 r2d2-diesel^1.01.0.0up to date
 reqwest^0.100.11.24out of date
 bigdecimal^0.10.4.2out of date
 num-traits^0.10.2.18out of date
 separator^0.30.4.1out of date
 iso_country^0.10.1.4up to date

Security Vulnerabilities

time: Potential segfault in the time crate

RUSTSEC-2020-0071

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.

The affected functions from time 0.2.7 through 0.2.22 are:

  • time::UtcOffset::local_offset_at
  • time::UtcOffset::try_local_offset_at
  • time::UtcOffset::current_local_offset
  • time::UtcOffset::try_current_local_offset
  • time::OffsetDateTime::now_local
  • time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

  • at
  • at_utc
  • now

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.

Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.

Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.

Workarounds

A possible workaround for crates affected through the transitive dependency in chrono, is to avoid using the default oldtime feature dependency of the chrono crate by disabling its default-features and manually specifying the required features instead.

Examples:

Cargo.toml:

chrono = { version = "0.4", default-features = false, features = ["serde"] }
chrono = { version = "0.4.22", default-features = false, features = ["clock"] }

Commandline:

cargo add chrono --no-default-features -F clock

Sources:

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

diesel: Fix a use-after-free bug in diesels Sqlite backend

RUSTSEC-2021-0037

We've misused sqlite3_column_name. The SQLite documentation states that the following:

The returned string pointer is valid until either the prepared statement is destroyed by sqlite3_finalize() or until the statement is automatically reprepared by the first call to sqlite3_step() for a particular run or until the next call to sqlite3_column_name() or sqlite3_column_name16() on the same column.

As part of our query_by_name infrastructure we've first received all field names for the prepared statement and stored them as string slices for later use. After that we called sqlite3_step() for the first time, which invalids the pointer and therefore the stored string slice.

lettre: SMTP command injection in body

RUSTSEC-2021-0069

Affected versions of lettre allowed SMTP command injection through an attacker's controlled message body. The module for escaping lines starting with a period wouldn't catch a period that was placed after a double CRLF sequence, allowing the attacker to end the current message and write arbitrary SMTP commands after it.

The flaw is fixed by correctly handling consecutive CRLF sequences.