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 haret

Dependencies

(16 total, 9 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 libc^0.10.2.153out of date
 time ⚠️*0.3.36maybe insecure
 uuid^0.51.8.0out of date
 rand^0.30.8.5out of date
 slog^12.7.0out of date
 amy^0.7.20.10.0out of date
 funfsm^0.20.2.1up to date
 orset^0.20.2.0up to date
 rabble^0.40.4.1up to date
 protobuf ⚠️^1.0.243.4.0out of date
 vertree^0.20.2.2up to date
 lazy_static^0.11.4.0out of date
 serde^1.01.0.202up to date
 serde_derive^1.01.0.202up to date
 rmp-serde^0.131.3.0out of date
 toml^0.40.8.13out of date

Dev dependencies

(5 total, 4 outdated)

CrateRequiredLatestStatus
 assert_matches^1.01.5.0up to date
 quickcheck^0.41.0.3out of date
 slog-envlogger^0.52.2.0out of date
 slog-stdlog^14.1.1out of date
 slog-term^1.12.9.1out of date

Crate haret-admin

Dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 rabble^0.40.4.1up to date
 rmp-serde^0.131.3.0out of date
 serde^1.01.0.202up to date
 uuid^0.51.8.0out of date

Crate haret-cli-client

Dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 uuid^0.51.8.0out of date
 lazy_static^0.11.4.0out of date

Crate haret-client

Dependencies

(1 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 protobuf ⚠️^1.0.243.4.0out of date

Crate haret-devconfig

No external dependencies! 🙌

Crate haret-server

Dependencies

(5 total, 4 outdated)

CrateRequiredLatestStatus
 rabble^0.40.4.1up to date
 slog^12.7.0out of date
 slog-envlogger^0.52.2.0out of date
 slog-stdlog^14.1.1out of date
 slog-term^1.12.9.1out of date

Security Vulnerabilities

protobuf: Out of Memory in stream::read_raw_bytes_into()

RUSTSEC-2019-0003

Affected versions of this crate called Vec::reserve() on user-supplied input.

This allows an attacker to cause an Out of Memory condition while calling the vulnerable method on untrusted data.

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: