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 spiffe

Dependencies

(20 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 simple_asn1 ⚠️^0.60.6.3maybe insecure
 hyper-util^0.1.80.1.17up to date
 jsonwebtoken^910.0.0out of date
 log^0.40.4.28up to date
 pkcs8^0.100.10.2up to date
 prost^0.140.14.1up to date
 prost-types^0.140.14.1up to date
 serde^11.0.228up to date
 serde_json^11.0.145up to date
 thiserror^22.0.17up to date
 time^0.30.3.44up to date
 tokio ⚠️^11.48.0maybe insecure
 tokio-stream^0.10.1.17up to date
 tokio-util^0.70.7.16up to date
 tonic^0.14.00.14.2up to date
 tonic-prost^0.140.14.2up to date
 tower^0.50.5.2up to date
 url^22.5.7up to date
 x509-parser^0.170.18.0out of date
 zeroize^11.8.2up to date

Dev dependencies

(4 total, 2 possibly insecure)

CrateRequiredLatestStatus
 jsonwebkey^0.30.3.5up to date
 once_cell^11.21.3up to date
 openssl ⚠️^0.100.10.74maybe insecure
 tokio ⚠️^11.48.0maybe insecure

Security Vulnerabilities

simple_asn1: Panic on incorrect date input to `simple_asn1`

RUSTSEC-2021-0125

Version 0.6.0 of the simple_asn1 crate panics on certain malformed inputs to its parsing functions, including from_der and der_decode. Because this crate is frequently used with inputs from the network, this should be considered a security vulnerability.

The issue occurs when parsing the old ASN.1 "UTCTime" time format. If an attacker provides a UTCTime where the first character is ASCII but the second character is above 0x7f, a string slice operation in the from_der_ function will try to slice into the middle of a UTF-8 character, and cause a panic.

This error was introduced in commit d7d39d709577710e9dc8, which updated simple_asn1 to use time instead of chrono because of RUSTSEC-2020-159. Versions of simple_asn1 before 0.6.0 are not affected by this issue.

The patch was applied in simple_asn1 version 0.6.1.

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

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.