# CVE-2020-10750: Information Exposure in jaeger

> Attackers with log access can discover Kafka credentials in Jaeger when using the Kafka data store, requiring an upgrade to fix.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-jaeger-2020-10750, GHSA-gh32-pc56-4c96, GO-2022-0834

## What is CVE-2020-10750?

CVE-2020-10750 is a high-severity vulnerability in the Jager project jaegertracing/jaeger, published on 19 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sensitive information written to a log file vulnerability was found in jaegertracing/jaeger before version 1.18.1 when the Kafka data store is used. This flaw allows an attacker with access to the container's log file to discover the Kafka credentials.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

4 open source packages ship an affected version, including github.com/jaegertracing/jaeger and jaeger. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/jaegertracing/jaeger` | Go | All versions | 1.18.1 |
| `github.com/jaegertracing/jaeger` | Go | All versions | 1.18.1 |
| `github.com/jaegertracing/jaeger` | Go | All versions | 1.18.1 |
| `jaeger` | Bitnami | All versions | 1.18.1 |

Products: Linuxfoundation Jaeger.

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

Upgrade github.com/jaegertracing/jaeger to 1.18.1 or later.

## Is CVE-2020-10750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10750 is a high-severity vulnerability in the Jager project jaegertracing/jaeger, published on 19 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10750 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/jaegertracing/jaeger (Go): affected all versions; fixed in 1.18.1
- github.com/jaegertracing/jaeger (Go): affected all versions; fixed in 1.18.1
- github.com/jaegertracing/jaeger (Go): affected all versions; fixed in 1.18.1
- jaeger (Bitnami): affected all versions; fixed in 1.18.1

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

## Sources

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

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