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 aos_data_proxy

Dependencies

(58 total, 18 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.811.0.100up to date
 async-channel^2.2.02.5.0up to date
 async-stream^0.3.50.3.6up to date
 async-trait^0.1.770.1.89up to date
 axum^0.7.40.8.8out of date
 aws-config^1.1.71.8.12up to date
 aws-sdk-s3^1.17.01.119.0up to date
 aws-smithy-http^0.60.60.62.6out of date
 base64^0.22.00.22.1up to date
 byteorder^1.5.01.5.0up to date
 bytes^1.5.01.11.0up to date
 chrono^0.4.340.4.42up to date
 dotenvy^0.15.70.15.7up to date
 futures^0.3.300.3.31up to date
 futures-channel^0.3.300.3.31up to date
 futures-core^0.3.300.3.31up to date
 futures-util^0.3.300.3.31up to date
 hex^0.4.30.4.3up to date
 hmac^0.12.10.12.1up to date
 http^0.2.121.4.0out of date
 hyper^0.14.281.8.1out of date
 md-5^0.10.60.10.6up to date
 rand^0.8.50.9.2out of date
 reqwest^0.11.250.13.1out of date
 s3s^0.9.00.12.0out of date
 serde^1.0.1971.0.228up to date
 sha2^0.10.80.10.9up to date
 tokio^1.36.01.49.0up to date
 tokio-stream^0.1.140.1.18up to date
 tower^0.4.130.5.2out of date
 tonic^0.11.00.14.2out of date
 tracing^0.1.400.1.44up to date
 tracing-subscriber ⚠️^0.3.180.3.22maybe insecure
 url^2.5.02.5.8up to date
 zstd^0.13.00.13.3up to date
 diesel-ulid^0.3.10.3.2up to date
 tokio-postgres^0.7.100.7.15up to date
 postgres-types^0.2.60.2.11up to date
 postgres_array^0.11.10.11.1up to date
 deadpool-postgres^0.12.10.14.1out of date
 postgres-from-row=0.5.20.5.2up to date
 dashmap^5.5.36.1.0out of date
 ahash^0.8.110.8.12up to date
 jsonwebtoken^9.2.010.2.0out of date
 prost-wkt-types^0.5.00.7.1out of date
 time^0.3.340.3.44up to date
 digest^0.10.70.10.7up to date
 reqsign^0.14.90.18.1out of date
 serde_json^1.0.1141.0.149up to date
 crossbeam-skiplist^0.1.30.1.3up to date
 lazy_static^1.4.01.5.0up to date
 toml^0.8.110.9.11+spec-1.1.0out of date
 cel-interpreter^0.6.00.10.0out of date
 cel-parser^0.6.00.10.1out of date
 nom^7.1.38.0.0out of date
 mime_guess^2.0.42.0.5up to date
 curve25519-dalek ⚠️^4.1.24.1.3maybe insecure
 ed25519-dalek^2.1.12.2.0up to date

Security Vulnerabilities

curve25519-dalek: Timing variability in `curve25519-dalek`'s `Scalar29::sub`/`Scalar52::sub`

RUSTSEC-2024-0344

Timing variability of any kind is problematic when working with potentially secret values such as elliptic curve scalars, and such issues can potentially leak private keys and other secrets. Such a problem was recently discovered in curve25519-dalek.

The Scalar29::sub (32-bit) and Scalar52::sub (64-bit) functions contained usage of a mask value inside a loop where LLVM saw an opportunity to insert a branch instruction (jns on x86) to conditionally bypass this code section when the mask value is set to zero as can be seen in godbolt:

A similar problem was recently discovered in the Kyber reference implementation:

https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/hqbtIGFKIpU/m/cnE3pbueBgAJ

As discussed on that thread, one portable solution, which is also used in this PR, is to introduce a volatile read as an optimization barrier, which prevents the compiler from optimizing it away.

The fix can be validated in godbolt here:

The problem was discovered and the solution independently verified by Alexander Wagner [email protected] and Lea Themint [email protected] using their DATA tool:

https://github.com/Fraunhofer-AISEC/DATA

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.