JLSEC-2026-1389: Heap buffer overflow when `read_command` on a collection fails in Mongoc.jl
Description
Mongoc.readcommand(collection, command) called the wrong libmongoc function. Its binding for mongoccollectionreadcommandwithopts called mongoccollectioncommandsimple, which takes one argument fewer, so libmongoc read every argument after readprefs one place early. libmongoc wrote its bsonerrort into the reply document, wrote the reply into the caller's options document (or discarded it when no options were given), and never filled in the error that Mongoc.jl reads, so the exception thrown for a failure carried no error code or message.
The reply document is a 128-byte bsont that bsonnew allocates on the C heap. A bsonerrort is 512 bytes. When the command fails, libmongoc writes to the last byte of the error, 384 bytes past the end of the allocation. A message longer than about 120 bytes also writes its text past the end. The message comes from the MongoDB server or from libmongoc, and server messages can echo parts of the command: the error for an unknown query operator includes the operator's name.
Calls that succeeded returned an empty document instead of the reply. A call with options overwrote the caller's options document with the reply.
Only readcommand(collection, ...) is affected. A comparison of all of the package's ccalls with the libmongoc headers found no other wrong function or argument count.
Impact
Each failing readcommand(collection, ...) call corrupts the C heap of the Julia process. This can crash the process or corrupt unrelated memory. A malicious or compromised MongoDB server controls the text written past the allocation. When an application builds the command from user input, that user can influence the text too. No exploit beyond heap corruption was demonstrated.
Patches
Fixed in Mongoc.jl 0.10.2, which calls mongoccollectionreadcommandwithopts. Upgrade to 0.10.2 or later.
Workarounds
Mongoc.readcommand(collection.database, command; options) runs the same command through the database binding, which calls the correct function.
Credits
The binding error was found and fixed by hhaensel in Mongoc.jl pull request #162. The out-of-bounds write was found while that fix was reviewed.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
julia/Mongocto a version that resolves this vulnerability.Fixed in 0.10.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.10.2