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

Crate constellation-server

Dependencies

(24 total, 8 outdated, 2 insecure)

CrateRequiredLatestStatus
 log^0.40.4.34up to date
 toml^0.81.1.6+spec-1.1.0out of date
 clap^4.54.6.7up to date
 lazy_static^1.41.5.0up to date
 serde^1.01.0.229up to date
 serde_derive^1.01.0.229up to date
 serde_json^1.01.0.151up to date
 url_serde^0.20.2.0up to date
 regex^1.101.13.1up to date
 async-trait^0.10.1.92up to date
 bb8-redis^0.150.26.0out of date
 actix-web^4.84.15.0up to date
 actix-web-httpauth^0.80.8.3up to date
 hickory-server^0.240.26.3out of date
 hickory-proto ⚠️^0.240.26.3insecure
 hickory-resolver^0.240.26.3out of date
 tokio^1.381.53.1up to date
 rand^0.80.10.3out of date
 farmhash^1.11.1.5up to date
 http_req^0.100.14.6out of date
 maxminddb ⚠️^0.240.32.0insecure
 tempfile^3.13.27.0up to date
 flate2^1.01.1.10up to date
 tar^0.40.4.46up 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.