Deps.rs

sqlx-postgres 0.8.6

[![dependency status](https://deps.rs/crate/sqlx-postgres/0.8.6/status.svg)](https://deps.rs/crate/sqlx-postgres/0.8.6)

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 sqlx-postgres

Dependencies

(39 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 atoi^2.02.0.0up to date
 base64^0.22.00.22.1up to date
 bigdecimal^0.4.00.4.10up to date
 bit-vec^0.6.30.8.0out of date
 bitflags^22.11.0up to date
 byteorder^1.4.31.5.0up to date
 chrono^0.4.340.4.44up to date
 crc^3.0.03.4.0up to date
 dotenvy^0.15.70.15.7up to date
 etcetera^0.8.00.11.0out of date
 futures-channel^0.3.190.3.32up to date
 futures-core^0.3.190.3.32up to date
 futures-util^0.3.190.3.32up to date
 hex^0.4.30.4.3up to date
 hkdf^0.12.00.12.4up to date
 hmac^0.12.00.12.1up to date
 home^0.5.50.5.12up to date
 ipnet^2.3.02.12.0up to date
 ipnetwork^0.20.00.21.1out of date
 itoa^1.0.11.0.17up to date
 log^0.4.180.4.29up to date
 mac_address^1.1.51.1.8up to date
 md-5^0.10.00.10.6up to date
 memchr^2.4.12.8.0up to date
 num-bigint^0.4.30.4.6up to date
 once_cell^1.9.01.21.3up to date
 rand^0.8.40.10.0out of date
 rust_decimal^1.26.11.40.0up to date
 serde^1.0.1441.0.228up to date
 serde_json^1.0.851.0.149up to date
 sha2^0.10.00.10.9up to date
 smallvec^1.7.01.15.1up to date
 sqlx-core=0.8.60.8.6up to date
 stringprep^0.1.20.1.5up to date
 thiserror^2.0.02.0.18up to date
 time ⚠️^0.3.360.3.47maybe insecure
 tracing^0.1.370.1.44up to date
 uuid^1.1.21.22.0up to date
 whoami ⚠️^1.2.12.1.1out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 sqlx=0.8.60.8.6up to date

Security Vulnerabilities

whoami: Stack buffer overflow with whoami on several Unix platforms

RUSTSEC-2024-0020

With versions of the whoami crate >= 0.5.3 and < 1.5.0, calling any of these functions leads to an immediate stack buffer overflow on illumos and Solaris:

  • whoami::username
  • whoami::realname
  • whoami::username_os
  • whoami::realname_os

With versions of the whoami crate >= 0.5.3 and < 1.0.1, calling any of the above functions also leads to a stack buffer overflow on these platforms:

  • Bitrig
  • DragonFlyBSD
  • FreeBSD
  • NetBSD
  • OpenBSD

This occurs because of an incorrect definition of the passwd struct on those platforms.

As a result of this issue, denial of service and data corruption have both been observed in the wild. The issue is possibly exploitable as well.

This vulnerability also affects other Unix platforms that aren't Linux or macOS.

This issue has been addressed in whoami 1.5.0.

For more information, see this GitHub issue.

time: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.

Patches

A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.

Workarounds

Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.