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.
spotifyd(36 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| alsa | ^0.9.1 | 0.9.1 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| dbus | ^0.9 | 0.9.7 | up to date |
| dbus-tokio | ^0.7.3 | 0.7.6 | up to date |
| dbus-crossroads | ^0.5.0 | 0.5.2 | up to date |
| fern | ^0.7.0 | 0.7.1 | up to date |
| futures | ^0.3.15 | 0.3.31 | up to date |
| gethostname | ^1.0.0 | 1.0.2 | up to date |
| hex | ^0.4 | 0.4.3 | up to date |
| libc | ^0.2.82 | 0.2.174 | up to date |
| log | ^0.4.6 | 0.4.27 | up to date |
| serde | ^1.0.115 | 1.0.219 | up to date |
| sha-1 | ^0.10 | 0.10.1 | up to date |
| tokio | ^1.26.0 | 1.46.1 | up to date |
| tokio-stream | ^0.1.7 | 0.1.17 | up to date |
| url | ^2.2.2 | 2.5.4 | up to date |
| librespot-audio | ^0.6 | 0.6.0 | up to date |
| librespot-playback | ^0.6 | 0.6.0 | up to date |
| librespot-core | ^0.6 | 0.6.0 | up to date |
| librespot-discovery | ^0.6 | 0.6.0 | up to date |
| librespot-connect | ^0.6 | 0.6.0 | up to date |
| librespot-metadata | ^0.6 | 0.6.0 | up to date |
| librespot-protocol | ^0.6 | 0.6.0 | up to date |
| librespot-oauth | ^0.6 | 0.6.0 | up to date |
| toml | ^0.8.19 | 0.8.23 | up to date |
| color-eyre | ^0.6 | 0.6.5 | up to date |
| directories | ^6.0.0 | 6.0.0 | up to date |
| thiserror | ^2.0 | 2.0.12 | up to date |
| time | ^0.3.37 | 0.3.41 | up to date |
| clap | ^4.5.23 | 4.5.40 | up to date |
| serde_ignored | ^0.1.10 | 0.1.12 | up to date |
| daemonize | ^0.5 | 0.5.0 | up to date |
| syslog | ^7 | 7.0.0 | up to date |
| whoami ⚠️ | ^1 | 1.6.0 | maybe insecure |
| pledge | ^0.4.2 | 0.4.2 | up to date |
| aws-lc-rs | ^1.12.6 | 1.13.1 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.11 | 0.11.8 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
whoami: Stack buffer overflow with whoami on several Unix platformsWith 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::usernamewhoami::realnamewhoami::username_oswhoami::realname_osWith 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:
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.