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 cookie_store

Dependencies

(9 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 cookie^0.14.10.15.1out of date
 idna^0.2.00.2.3up to date
 indexmap^1.4.01.7.0up to date
 log^0.4.80.4.14up to date
 publicsuffix^1.5.42.1.1out of date
 serde^1.0.1111.0.130up to date
 serde_json^1.0.551.0.68up to date
 time ⚠️^0.2.160.3.2out of date
 url^2.1.12.2.2up to date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.7.10.9.0out of date
 pretty_assertions^0.6.10.7.2out of 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 the user to set any environment variable in a different thread than the affected functions.

The affected functions 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

Non-Unix targets are unaffected. This includes Windows and wasm.

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 a the updated, unaffected code.

Workarounds

No workarounds are known.

References

#293