Skip to content
Fencer Intel
low —

GHSA-mj73-j457-8x9q json

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

published 11mo ago modified 11mo ago also RUSTSEC-2025-0132

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

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.

Patch / fix

  • crates.io maxminddb 0.27.0

Is GHSA-mj73-j457-8x9q in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io maxminddb
>=0.11.0, <0.27.0
0.27.0

Classification

Weakness
  • CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.