Deps.rs

cocool97 / adb_client

[![dependency status](https://deps.rs/repo/github/cocool97/adb_client/status.svg)](https://deps.rs/repo/github/cocool97/adb_client)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate adb_cli

Dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 adb_client^3.0.13.0.1up to date
 clap^4.5.544.5.54up to date
 env_logger^0.11.80.11.8up to date
 log^0.4.290.4.29up to date
 tabwriter^1.4.11.4.1up to date
 termios^0.3.30.3.3up to date

Crate adb_client

Dependencies

(19 total, 1 outdated, 1 insecure)

CrateRequiredLatestStatus
 base64^0.22.10.22.1up to date
 byteorder^1.5.01.5.0up to date
 chrono^0.4.430.4.43up to date
 image^0.25.90.25.9up to date
 log^0.4.290.4.29up to date
 num-bigint-dig^0.8.60.9.1out of date
 num-traits^0.2.190.2.19up to date
 quick-protobuf^0.8.10.8.1up to date
 rand^0.9.20.9.2up to date
 rcgen^0.14.60.14.7up to date
 regex^1.12.21.12.2up to date
 rsa ⚠️^0.9.100.9.10insecure
 rustls^0.23.360.23.36up to date
 rustls-pki-types^1.14.01.14.0up to date
 sha1^0.10.60.10.6up to date
 thiserror^2.0.182.0.18up to date
 mdns-sd^0.17.20.17.2up to date
 rusb^0.9.40.9.4up to date
 num_enum^0.7.50.7.5up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^1.0.1001.0.100up to date
 criterion^0.8.10.8.1up to date

Crate mdns

No external dependencies! 🙌

Crate pyadb_client

Dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^1.0.1001.0.100up to date
 pyo3^0.27.20.27.2up to date
 pyo3-stub-gen^0.17.20.17.2up to date
 pyo3-stub-gen-derive^0.17.20.17.2up to date

Security Vulnerabilities

rsa: Marvin Attack: potential key recovery through timing sidechannels

RUSTSEC-2023-0071

Impact

Due to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.

Patches

No patch is yet available, however work is underway to migrate to a fully constant-time implementation.

Workarounds

The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.

References

This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.