# CVE-2020-7021: Insertion of Sensitive Information into Log File in Elasticsearch

> Administrators can view sensitive data like password hashes in audit logs if request body emission is enabled.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-elasticsearch-2020-7021, GHSA-cqgv-256r-m9r8, UBUNTU-CVE-2020-7021

## What is CVE-2020-7021?

CVE-2020-7021 is a medium-severity vulnerability in Elastic Elasticsearch, published on 10 Feb 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Elasticsearch versions before 7.10.0 and 6.8.14 have an information disclosure issue when audit logging and the emit_request_body option is enabled. The Elasticsearch audit log could contain sensitive information such as password hashes or authentication tokens. This could allow an Elasticsearch administrator to view these details.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2020-7021?

5 open source packages ship an affected version, including org.elasticsearch:elasticsearch and elasticsearch. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.elasticsearch:elasticsearch` | Maven | All versions | 6.8.14 |
| `org.elasticsearch:elasticsearch` | Maven | All versions | 6.8.14 |
| `org.elasticsearch:elasticsearch` | Maven | From 7.0.0 | 7.10.0 |
| `org.elasticsearch:elasticsearch` | Maven | From 7.0.0 | 7.10.0 |
| `elasticsearch` | Bitnami | All versions | 6.8.14, 7.10.0 |

Products: Elastic Elasticsearch.

## How do I fix CVE-2020-7021?

Upgrade org.elasticsearch:elasticsearch to a fixed version for your release line: 6.8.14 or 7.10.0.

## Is CVE-2020-7021 being exploited?

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

## Other vulnerabilities in Elastic Elasticsearch

- [CVE-2015-1427](https://insights.sbomify.com/CVE-2015-1427/): Elasticsearch Groovy Scripting Engine Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2014-3120](https://insights.sbomify.com/CVE-2014-3120/): Elasticsearch Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2015-5377](https://insights.sbomify.com/CVE-2015-5377/): Code injection in n/a (critical 9.8)
- [CVE-2026-72649](https://insights.sbomify.com/CVE-2026-72649/): Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution (high 8.8)
- [CVE-2026-72642](https://insights.sbomify.com/CVE-2026-72642/): Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7021 and fix it if it is affected.

What it is: CVE-2020-7021 is a medium-severity vulnerability in Elastic Elasticsearch, published on 10 Feb 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7021 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.elasticsearch:elasticsearch (Maven): affected all versions; fixed in 6.8.14
- org.elasticsearch:elasticsearch (Maven): affected all versions; fixed in 6.8.14
- org.elasticsearch:elasticsearch (Maven): affected from 7.0.0; fixed in 7.10.0
- org.elasticsearch:elasticsearch (Maven): affected from 7.0.0; fixed in 7.10.0
- elasticsearch (Bitnami): affected all versions; fixed in 6.8.14, 7.10.0

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-2020-7021/ (Markdown: https://insights.sbomify.com/CVE-2020-7021/index.md)
```

## Sources

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

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