CVE-2020-10750 is a medium-severity (CVSS 5.5) Information Exposure vulnerability in github.com/jaegertracing/jaeger. A fix is available for github.com/jaegertracing/jaeger — see the affected versions and patch details below.
Information Exposure in jaeger
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/jaegertracing/jaegerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/jaegertracing/jaeger | all versions | 1.18.1go get github.com/jaegertracing/jaeger@v1.18.1 |
Affected Products
jaegerlinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jaegertracing/jaeger, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/jaegertracing/jaeger to 1.18.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10750 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
While OpenShift ServiceMesh Jaeger does package the affected code (Kafka), the only supported data store is ElasticSearch. Additionally, in the documentation and notes, only ElasticSearch is supported, marking OpenShift ServiceMesh as affected but WONTFIX.
| Product | Fixed in | Advisory |
|---|---|---|
| Jaeger-1.17 | distributed-tracing/jaeger-all-in-one-rhel7:1.17.3-2 | RHSA-2020:2636 |
Frequently Asked Questions
Is CVE-2020-10750 in your dependencies?
Find it across Go, including transitive dependencies.