CVE-2024-6375 json
Missing authorization check may lead to shard key refinement
published 2024-07-01 2 y ago modified 2026-09-10 59 d ago also BIT-mongodb-2024-6375 , EUVD-2024-47482
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
A command for refining a collection shard key is missing an authorization check. This may cause the command to run directly on a shard, leading to either degradation of query performance, or to revealing chunk boundaries through timing side channels. This affects MongoDB Server v5.0 versions, prior to 5.0.22, MongoDB Server v6.0 versions, prior to 6.0.11 and MongoDB Server v7.0 versions prior to 7.0.3.
Patch / fix
- bitnami mongodb 5.0.22, 6.0.11, 7.0.3
- MongoDB Inc MongoDB Server 5.0.22, 6.0.11, 7.0.3
- jira.mongodb.org/browse/SERVER-79327 advisory
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L |
| OSV | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mongodb | >=5.0.0, <5.0.22 >=6.0.0, <6.0.11 >=7.0.0, <7.0.3 |
5.0.22 6.0.11 7.0.3 |
Affected products
- MongoDB Inc MongoDB Server
Classification
- Weakness
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-79327
issue-tracking, patch, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-6375
web
Sources
- CVE List CVE-2024-6375
- NVD CVE-2024-6375
- OSV BIT-mongodb-2024-6375
Fencer Vulns 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.