First published: Mon Oct 28 2024(Updated: )
A bug in query analysis of certain complex self-referential $lookup subpipelines may result in literal values in expressions for encrypted fields to be sent to the server as plaintext instead of ciphertext. Should this occur, no documents would be returned or written. This issue affects mongocryptd binary (v5.0 versions prior to 5.0.29, v6.0 versions prior to 6.0.17, v7.0 versions prior to 7.0.12 and v7.3 versions prior to 7.3.4) and mongo_crypt_v1.so shared libraries (v6.0 versions prior to 6.0.17, v7.0 versions prior to 7.0.12 and v7.3 versions prior to 7.3.4) released alongside MongoDB Enterprise Server versions.
Credit: cna@mongodb.com
Affected Software | Affected Version | How to fix |
---|---|---|
MongoDB | >=6.0.0<6.0.17 | |
MongoDB | >=7.0.0<7.0.12 | |
MongoDB | >=7.3.0<7.3.4 | |
MongoDB | >=5.0.0<5.0.29 | |
MongoDB | >=6.0.0<6.0.17 | |
MongoDB | >=7.0.0<7.0.12 | |
MongoDB | >=7.3.0<7.3.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-8013 has a moderate severity rating as it can lead to sensitive information being exposed.
To fix CVE-2024-8013, upgrade your MongoDB software to versions that are not affected by this vulnerability.
CVE-2024-8013 affects MongoDB versions between 6.0.0 and 6.0.17, 7.0.0 and 7.0.12, and 7.3.0 and 7.3.4 for both mongo_crypt_v1.so and mongocryptd.
CVE-2024-8013 may cause encrypted field values to be sent as plaintext, potentially exposing sensitive information.
Yes, as a temporary workaround, you may avoid using the specific complex self-referential $lookup subpipelines until a patch is applied.