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 signup-sequencer

Dependencies

(43 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.681.0.97up to date
 async-stream^0.3.30.3.6up to date
 async-trait^0.1.860.1.88up to date
 axum^0.7.70.8.1out of date
 axum-server^0.7.10.7.2up to date
 tower-http^0.6.10.6.2up to date
 bytes^1.4.01.10.1up to date
 bon^33.5.1up to date
 chrono ⚠️^0.4.190.4.40maybe insecure
 clap^4.04.5.32up to date
 config^0.13.40.15.11out of date
 ethers^2.0.102.0.14up to date
 ethers-solc^2.0.102.0.14up to date
 eyre ⚠️^0.60.6.12maybe insecure
 futures^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 hex^0.4.30.4.3up to date
 hex-literal^0.4.11.0.0out of date
 humantime^2.1.02.2.0up to date
 humantime-serde^1.1.11.1.1up to date
 hyper^1.4.11.6.0up to date
 indoc^2.0.42.0.6up to date
 once_cell^1.81.21.1up to date
 prometheus^0.13.30.13.4up to date
 reqwest^0.12.80.12.15up to date
 ruint^1.12.31.13.1up to date
 semaphore-rs^0.3.20.3.2up to date
 semaphore-rs-poseidon^0.3.20.3.2up to date
 semaphore-rs-trees^0.3.20.3.2up to date
 semaphore-rs-hasher^0.3.20.3.2up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 sqlx^0.8.20.8.3up to date
 take_mut^0.2.20.2.2up to date
 tempfile^3.5.03.19.1up to date
 thiserror^1.02.0.12out of date
 tokio^1.381.44.1up to date
 toml^0.8.80.8.20up to date
 tracing^0.10.1.41up to date
 tracing-futures^0.20.2.5up to date
 url^2.22.5.4up to date
 zeroize^1.6.01.8.1up to date
 dotenvy^0.15.00.15.7up to date

Dev dependencies

(11 total, 2 outdated)

CrateRequiredLatestStatus
 hex^0.4.30.4.3up to date
 lazy_static^1.4.01.5.0up to date
 maplit^1.0.21.0.2up to date
 regex^1.7.11.11.1up to date
 semaphore-rs^0.3.10.3.2up to date
 similar-asserts^1.5.01.7.0up to date
 test-case^3.03.3.1up to date
 testcontainers^0.15.00.23.3out of date
 testcontainers-modules^0.3.70.11.6out of date
 tracing-subscriber^0.3.110.3.19up to date
 tracing-test^0.20.2.5up to date

Crate oz-api

Dependencies

(11 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.97up to date
 chrono^0.4.230.4.40up to date
 ethers^2.0.102.0.14up to date
 hyper^0.14.171.6.0out of date
 reqwest^0.11.140.12.15out of date
 serde^1.0.1541.0.219up to date
 serde_json^1.0.941.0.140up to date
 thiserror^1.0.392.0.12out of date
 tokio ⚠️^1.171.44.1maybe insecure
 tracing^0.1.370.1.41up to date
 url^2.3.12.5.4up to date

Crate tx-sitter-client

Dependencies

(7 total, 1 outdated)

CrateRequiredLatestStatus
 anyhow^1.01.0.97up to date
 ethers^2.0.102.0.14up to date
 reqwest^0.12.80.12.15up to date
 serde^1.0.1541.0.219up to date
 serde_json^1.0.941.0.140up to date
 strum^0.250.27.1out of date
 tracing^0.10.1.41up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 indoc^22.0.6up to date

Crate micro-oz

Dependencies

(12 total, 2 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.721.0.97up to date
 async-trait^0.1.710.1.88up to date
 axum^0.6.190.8.1out of date
 chrono^0.4.260.4.40up to date
 clap^4.3.144.5.32up to date
 ethers^2.0.102.0.14up to date
 hyper^0.14.271.6.0out of date
 serde^1.0.1711.0.219up to date
 serde_json^1.0.1031.0.140up to date
 tokio^1.29.11.44.1up to date
 tracing^0.1.370.1.41up to date
 tracing-subscriber^0.3.170.3.19up to date

Crate postgres-docker-utils

Dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.97up to date
 test-case^3.1.03.3.1up to date
 tokio ⚠️^1.01.44.1maybe insecure
 testcontainers^0.15.00.23.3out of date
 testcontainers-modules^0.3.70.11.6out of date

Crate e2e-tests

Dependencies

(14 total, 3 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.681.0.97up to date
 ethers^2.0.102.0.14up to date
 hex^0.4.30.4.3up to date
 hex-literal^0.4.11.0.0out of date
 hyper^0.14.171.6.0out of date
 rand^0.8.50.9.0out of date
 retry^2.0.02.0.0up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 tokio^1.381.44.1up to date
 tracing^0.10.1.41up to date
 tracing-futures^0.20.2.5up to date
 tracing-subscriber^0.3.110.3.19up to date
 tracing-test^0.20.2.5up to date

Crate cognitoauth

Dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 aws-config^1.5.61.6.0up to date
 aws-sdk-cognitoidentityprovider^1.51.01.73.1up to date
 aws-smithy-client^0.60.30.60.3up to date
 cognito_srp^0.1.10.1.2up to date
 thiserror^1.0.322.0.12out of date
 tracing^0.10.1.41up 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);

eyre: Parts of Report are dropped as the wrong type during downcast

RUSTSEC-2024-0021

In affected versions, after a Report is constructed using wrap_err or wrap_err_with to attach a message of type D onto an error of type E, then using downcast to recover ownership of either the value of type D or the value of type E, one of two things can go wrong:

  • If downcasting to E, there remains a value of type D to be dropped. It is incorrectly "dropped" by running E's drop behavior, rather than D's. For example if D is &str and E is std::io::Error, there would be a call of std::io::Error::drop in which the reference received by the Drop impl does not refer to a valid value of type std::io::Error, but instead to &str.

  • If downcasting to D, there remains a value of type E to be dropped. When D and E do not happen to be the same size, E's drop behavior is incorrectly executed in the wrong location. The reference received by the Drop impl may point left or right of the real E value that is meant to be getting dropped.

In both cases, when the Report contains an error E that has nontrivial drop behavior, the most likely outcome is memory corruption.

When the Report contains an error E that has trivial drop behavior (for example a Utf8Error) but where D has nontrivial drop behavior (such as String), the most likely outcome is that downcasting to E would leak D.