CVE-2024-6375: Missing authorization check may lead to shard key refinement
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MongoDB Serverto a version that resolves this vulnerability.Fixed in 5.0.22 - Upgrade
Upgrade
MongoDB Serverto a version that resolves this vulnerability.Fixed in 6.0.11 - Upgrade
Upgrade
MongoDB Serverto a version that resolves this vulnerability.Fixed in 7.0.3
Event History
Frequently Asked Questions
What is the severity of CVE-2024-6375?
CVE-2024-6375 is classified as a high severity vulnerability due to its potential impact on query performance and data exposure.
How do I fix CVE-2024-6375?
To fix CVE-2024-6375, upgrade to MongoDB Server version 5.0.22 or later, 6.0.11 or later, or 7.0.3 or later.
What is the impact of CVE-2024-6375 on MongoDB Server?
CVE-2024-6375 may lead to degraded query performance and the potential exposure of chunk boundaries through timing side channels.
Which versions of MongoDB Server are affected by CVE-2024-6375?
CVE-2024-6375 affects MongoDB Server versions from 5.0.0 up to 5.0.22, 6.0.0 up to 6.0.11, and 7.0.0 up to 7.0.3.
Does CVE-2024-6375 require immediate action?
Yes, due to its severity and potential impact, immediate action is recommended to upgrade to a non-affected version.