Skip to content
Fencer Intel
medium 6.8

CVE-2024-10921 json

Improper neutralization of null bytes may lead to buffer over-reads in MongoDB Server

published 2y ago modified 2mo ago also BIT-mongodb-2024-10921 , EUVD-2024-33350

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

An authorized user may trigger crashes or receive the contents of buffer over-reads of Server memory by issuing specially crafted requests that construct malformed BSON in the MongoDB Server. This issue affects MongoDB Server v5.0 versions prior to 5.0.30 , MongoDB Server v6.0 versions prior to 6.0.19, MongoDB Server v7.0 versions prior to 7.0.15 and MongoDB Server v8.0 versions prior to and including 8.0.2.

Patch / fix

  • bitnami mongodb 5.0.30, 6.0.19, 7.0.15, 8.0.3
  • MongoDB Inc MongoDB Server 5.0.30, 6.0.19, 7.0.15, 8.0.3

Is CVE-2024-10921 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
OSV 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami mongodb
>=5.0.0, <5.0.30
>=6.0.0, <6.0.19
>=7.0.0, <7.0.15
>=8.0.0, <8.0.3
5.0.30
6.0.19
7.0.15
8.0.3

Affected products

  • MongoDB Inc MongoDB Server

Classification

Weakness
  • CWE-158 Improper Neutralization of Null Byte or NUL Character
Technology feeds

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.