# CVE-2024-8013: CSFLE and Queryable Encryption self-lookup may fail to encrypt values in subpipelines

> A bug in MongoDB's query analysis may send encrypted field values as plaintext to the server, potentially exposing sensitive data.

- **Severity:** Low 2.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Oct 2024
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-mpw3-23h3-rhrx

## What is CVE-2024-8013?

CVE-2024-8013 is a low-severity vulnerability in MongoDB Inc Mongo_crypt_v1.so, published on 28 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### 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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2024-8013?

It affects 2 products.


Products: Mongodb Mongo Crypt V1.so, Mongodb Mongocryptd.

## How do I fix CVE-2024-8013?

No fix has been published for CVE-2024-8013 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-8013 being exploited?

There is no known exploitation of CVE-2024-8013 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8013 and fix it if it is affected.

What it is: CVE-2024-8013 is a low-severity vulnerability in MongoDB Inc Mongo_crypt_v1.so, published on 28 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-8013 in the wild and no public exploit code.

Affected product: MongoDB Inc Mongo_crypt_v1.so. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8013/ (Markdown: https://insights.sbomify.com/CVE-2024-8013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8013
- OSV: https://osv.dev/vulnerability/CVE-2024-8013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8013/
Summaries are generated and may contain mistakes; the official description above is the record.