MongoDB Java Driver vulnerabilities

The BSON encoding component of the MongoDB Java Driver does not verify that an externally supplied raw document's declared length matches the actual byte range before copying it into a database command. An application processing untrusted bytes can emit a structurally inconsistent message, causing the database to interpret trailing content as additional command fields, potentially altering data read or written.

Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB Java Driver causes a caller-supplied structured file identifier to be interpreted as a query condition rather than a literal identifier. An authenticated user who can influence the identifier may obtain stored file content beyond the intended target, cause all GridFS file chunks in the affected bucket to be removed, or rename a stored file other than the intended target.

A use-after-free in the reactive client-side encryption component of the MongoDB Java Driver can cause native resources to be freed while an affected encrypted operation is still using them when the operation is cancelled. A party able to cause such an operation to be cancelled may cause the hosting application process to terminate. Reaching the issue requires an affected reactive encryption configuration that retrieves KMS credentials on demand.