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

Crate leaf

Dependencies

(70 total, 30 outdated, 2 insecure)

CrateRequiredLatestStatus
 tokio^11.53.1up to date
 protobuf^3.63.7.2up to date
 thiserror^1.02.0.20out of date
 futures^0.30.3.34up to date
 async-trait^0.10.1.92up to date
 bytes^11.12.1up to date
 lazy_static^1.51.5.0up to date
 anyhow^1.01.0.104up to date
 rand^0.80.10.2out of date
 socket2^0.50.6.5out of date
 async-recursion^1.11.1.1up to date
 parking_lot^0.120.12.5up to date
 uuid^11.26.1up to date
 hickory-proto ⚠️^0.240.26.3insecure
 lru^0.120.18.4out of date
 tracing^0.10.1.44up to date
 tracing-appender^0.20.2.5up to date
 tracing-subscriber^0.30.3.23up to date
 chrono^0.40.4.45up to date
 maxminddb ⚠️^0.240.32.0insecure
 memmap2^0.90.9.11up to date
 cidr^0.20.3.2out of date
 regex^1.111.13.1up to date
 directories^4.06.0.0out of date
 async-ffi^0.20.5.1out of date
 libloading^0.70.9.0out of date
 serde_json^1.01.0.151up to date
 serde_derive^1.01.0.229up to date
 serde^1.01.0.229up to date
 openssl^0.100.10.81up to date
 ring^0.170.17.14up to date
 aws-lc-rs^1.161.18.1up to date
 tokio-rustls^0.260.26.5up to date
 webpki-roots^0.251.0.9out of date
 rustls-pemfile^1.02.2.0out of date
 openssl-probe^0.10.2.1out of date
 tokio-openssl^0.60.6.5up to date
 tungstenite^0.240.30.0out of date
 tokio-tungstenite^0.240.30.0out of date
 url^2.52.5.8up to date
 http^1.11.5.0up to date
 async-socks5^0.60.6.0up to date
 hkdf^0.120.13.0out of date
 md-5^0.100.11.0out of date
 sha-1^0.100.10.1up to date
 percent-encoding^2.32.3.2up to date
 base64^0.220.23.1out of date
 memchr^22.8.3up to date
 sha2^0.100.11.0out of date
 hex^0.40.4.3up to date
 lz_fnv^0.10.1.2up to date
 cfb-mode^0.80.9.1out of date
 hmac^0.120.13.0out of date
 aes^0.80.9.3out of date
 aes-gcm^0.100.11.1out of date
 sha3^0.100.12.0out of date
 digest^0.100.11.3out of date
 byteorder^11.5.0up to date
 crc32fast^11.5.2up to date
 lru_time_cache^0.110.11.11up to date
 tokio-util^0.70.7.19up to date
 quinn^0.110.11.12up to date
 rustls^0.230.23.45up to date
 axum^0.70.8.9out of date
 notify^68.2.0out of date
 tun^0.70.8.14out of date
 ipconfig^0.30.3.4up to date
 jni^0.210.22.4out of date
 pnet_datalink^0.340.35.0out of date
 libc^0.20.2.189up to date

Dev dependencies

(3 total, 2 outdated)

CrateRequiredLatestStatus
 rcgen^0.130.14.10out of date
 sha2^0.100.11.0out of date
 tokio^11.53.1up to date

Build dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 cc^1.21.4.7up to date
 bindgen^0.720.73.2out of date
 protobuf-codegen=3.6.03.7.2out of date
 protoc-bin-vendored^3.23.2.0up to date

Crate leaf-cli

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 tokio^11.53.1up to date
 argh^0.10.1.19up to date

Crate leaf-ffi

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 tokio^11.53.1up to date
 anyhow^1.01.0.104up to date
 futures^0.30.3.34up to date

Crate shadowsocks

Dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 async-trait^0.10.1.92up to date
 tokio^11.53.1up to date
 async-ffi^0.20.5.1out of date
 bytes^11.12.1up to date

Security Vulnerabilities

maxminddb: `Reader::open_mmap` unsoundly marks unsafe memmap operation as safe

RUSTSEC-2025-0132

maxminddb prior to version 0.27 declared Reader::open_mmap as safe despite wrapping an inherently unsafe memmap2 operation with no extra step done to guarantee safety. This could have led to undefined behaviour if the file were to be modified on disk while the memory map was still active.

hickory-proto: CPU exhaustion during message encoding due to O(n²) name compression

RUSTSEC-2026-0119

During message encoding, hickory-proto's BinEncoder stores pointers to labels that are candidates for name compression in a Vec<(usize, Vec<u8>)>. The name compression logic then searches for matches with a linear scan.

A malicious message with many records can both introduce many candidate labels, and invoke this linear scan many times. This can amplify CPU exhaustion in DoS attacks.

This is similar to CVE-2024-8508.

We recommend all affected users update to hickory-proto 0.26.1 for the fix.