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 tenrankai

Dependencies

(43 total, 2 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.89up to date
 aws-config^11.8.11up to date
 aws-sdk-sesv2^11.106.0up to date
 axum^0.80.8.7up to date
 base64^0.220.22.1up to date
 hmac^0.120.12.1up to date
 chrono ⚠️^0.40.4.42maybe insecure
 clap^4.54.5.53up to date
 flate2^1.11.1.5up to date
 rexif^0.70.7.5up to date
 image^0.250.25.9up to date
 imageproc^0.250.25.0up to date
 ab_glyph^0.20.2.32up to date
 resvg^0.450.45.1up to date
 usvg^0.450.45.1up to date
 ico^0.40.5.0out of date
 webp^0.30.3.1up to date
 libwebp-sys^0.130.14.1out of date
 rgb^0.80.8.52up to date
 liquid^0.260.26.11up to date
 liquid-core^0.260.26.11up to date
 mime_guess^2.02.0.5up to date
 pulldown-cmark^0.130.13.0up to date
 rand^0.90.9.2up to date
 serde^1.01.0.228up to date
 serde_json^1.01.0.145up to date
 sha2^0.100.10.9up to date
 thiserror^2.02.0.17up to date
 tokio ⚠️^11.48.0maybe insecure
 tokio-util^0.70.7.17up to date
 toml_edit^0.230.23.9up to date
 tower^0.50.5.2up to date
 tower-http^0.60.6.8up to date
 tracing^0.10.1.43up to date
 httpdate^1.01.0.3up to date
 tracing-subscriber ⚠️^0.30.3.22maybe insecure
 url^2.52.5.7up to date
 urlencoding^2.12.1.3up to date
 uuid^1.181.19.0up to date
 walkdir^2.52.5.0up to date
 webauthn-rs^0.50.5.3up to date
 webauthn-rs-proto^0.50.5.3up to date
 env_logger^0.110.11.8up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^3.233.23.0up to date
 axum-test^18.218.4.1up 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

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);

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.