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 article_scraper

Dependencies

(16 total, 2 possibly insecure)

CrateRequiredLatestStatus
 base64^0.220.22.1up to date
 chrono ⚠️^0.40.4.45maybe insecure
 encoding_rs^0.80.8.35up to date
 escaper^0.10.1.1up to date
 futures^0.30.3.32up to date
 image^0.250.25.10up to date
 libxml^0.30.3.14up to date
 once_cell^1.211.21.4up to date
 regex^1.121.12.4up to date
 reqwest^0.130.13.4up to date
 rust-embed^8.118.11.0up to date
 thiserror^2.02.0.18up to date
 tokio ⚠️^11.52.3maybe insecure
 tracing^0.10.1.44up to date
 unic-emoji-char^0.90.9.0up to date
 url^2.52.5.8up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 test-log^0.20.2.21up to date
 tokio ⚠️^11.52.3maybe insecure

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

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);