RUSTSEC-2025-0132 (GHSA-MJ73-J457-8X9Q)
Vulnerability from osv_rustsec – Published: 2025-11-28 12:00 – Updated: 2025-12-02 06:03 – Source websitemaxminddb 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.
{
"affected": [
{
"database_specific": {
"categories": [
"memory-corruption"
],
"cvss": null,
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [
"maxminddb::Reader::open",
"maxminddb::Reader::open_mmap"
],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "maxminddb",
"purl": "pkg:cargo/maxminddb"
},
"ranges": [
{
"events": [
{
"introduced": "0.11.0"
},
{
"fixed": "0.27.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-mj73-j457-8x9q"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "maxminddb prior to version 0.27 declared `Reader::open_mmap` as safe \ndespite wrapping an inherently unsafe memmap2 operation with no\nextra step done to guarantee safety. This could have led to undefined\nbehaviour if the file were to be modified on disk while the memory map\nwas still active.",
"id": "RUSTSEC-2025-0132",
"modified": "2025-12-02T06:03:09Z",
"published": "2025-11-28T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/maxminddb"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2025-0132.html"
},
{
"type": "REPORT",
"url": "https://github.com/oschwald/maxminddb-rust/issues/86"
},
{
"type": "WEB",
"url": "https://github.com/oschwald/maxminddb-rust/commit/98f0e4fff9678c841ed33f3b8a46322f6163c32a"
}
],
"related": [],
"severity": [],
"summary": "`Reader::open_mmap` unsoundly marks unsafe memmap operation as safe"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.