Information Exposure Through Log Files Affecting kubeflow-pipelines package, versions <2.2.0-r3
Threat Intelligence
EPSS
0.04% (14th
percentile)
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-WOLFILATEST-KUBEFLOWPIPELINES-7221276
- published 7 Jun 2024
- disclosed 7 Dec 2020
Introduced: 7 Dec 2020
CVE-2020-8565 Open this link in a new tabHow to fix?
Upgrade Wolfi kubeflow-pipelines to version 2.2.0-r3 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kubeflow-pipelines package and not the kubeflow-pipelines package as distributed by Wolfi.
See How to fix? for Wolfi relevant fixed versions and status.
In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects <= v1.19.3, <= v1.18.10, <= v1.17.13, < v1.20.0-alpha2.
CVSS Scores
version 3.1