Duplicate geometry fields via unvalidated GeoJSON extra members
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.13.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The MongoDB C# Driver's GeoJSON serialization is affected, particularly in applications that let users supply field names for GeoJSON extra members. The flaw can cause stored location records to contain duplicate geometry fields, leading to inconsistent values between the server and the driver and making some records unreadable by the application.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The MongoDB C# Driver writes GeoJSON extra members without checking whether their names collide with reserved GeoJSON members such as type and coordinates. An application that places user-supplied field names into these extra members can store documents with duplicate geometry fields, so the server and the driver resolve different values for the same record. Affected records can also become unreadable through the driver, interrupting application code that reads them.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- MongoDB C# Driver
From 1.8.0 · fixed in 3.13.0