Sign inStart freeBook a demo

What is CVE-2024-8013?A low-severity flaw in Mongocryptd, explained.

Low severity2 affected products
The short answer

CVE-2024-8013 is a low-severity flaw (CVSS 3.3) in Mongocryptd from Mongodb, published on 28 October 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.1%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 28 October 2024. Record last updated 17 June 2026. We keep this page's data up to date.

What it does

What is CVE-2024-8013? In plain terms.

An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read some data.

The official description

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.

What kind of flaw is it?

  • CWE-319Cleartext Transmission of Sensitive Information
CVSS 3.1 scoreLow · 3.3

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAlready on the device
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstAn ordinary user account
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan read some data

Severity vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation

Is CVE-2024-8013 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.1%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days0.1%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
11out of 100Info

CVE-2024-8013 scores 11. Action: Track.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2024-8013 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2024-8013? 2 products.

The published record lists 2 products from 1 vendor. Versions are shown as published: "5.0.0 to before 5.0.29" means from 5.0.0 up to, but not including, 5.0.29. If you run one of these, check your version, then go to the fix below.

  • Application

    Mongocryptd

    by Mongodb

    Affected versions
    5.0.0 to before 5.0.296.0.0 to before 6.0.177.0.0 to before 7.0.127.3.0 to before 7.3.4
  • Application

    Mongo Crypt V1.so

    by Mongodb

    Affected versions
    6.0.0 to before 6.0.177.0.0 to before 7.0.127.3.0 to before 7.3.4
Remediation

How do I fix CVE-2024-8013? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

1 link
Precursor Intelligence

Does CVE-2024-8013 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2024-8013 is a low-severity flaw in Mongocryptd from Mongodb, published on 28 October 2024. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read some data.

It scores 3.3 out of 10 on the CVSS severity scale, which is low. Our risk score for CVE-2024-8013 is 11 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.1%. That can change at any time, which is why we keep watching.

For Mongocryptd from Mongodb: 5.0.0 to before 5.0.29, 6.0.0 to before 6.0.17, 7.0.0 to before 7.0.12, 7.3.0 to before 7.3.4. The record lists 2 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring