maxminddb's `Reader::open_mmap` unsoundly marks unsafe memmap operation as safe
Priority LOW 38CWE-915Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Tampering
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-915.
Summary
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.
Why it matters now
Fix Fixed maxminddb (crates.io): 0.27.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | maxminddb (crates.io) | 0.11.0 to before 0.27.0 | 0.27.0 | Patch available | GHSA-mj73-j457-8x9q |
- maxminddb (crates.io) Vendor— Affected 0.11.0 to before 0.27.0 Fixed in 0.27.0 Patch available GHSA-mj73-j457-8x9q
Remediation
- Fix · GHSA-mj73-j457-8x9q maxminddb (crates.io) Fixed in 0.27.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-mj73-j457-8x9q
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences