CVE-2019-25210: Infoleak

Published Mar 3, 2024
·
Updated

Withdrawn Advisory

This advisory has been withdrawn because the issue describes intended behavior and the output is not exposed to unauthorized users. This link has been maintained to preserve external references.

Original Description

An issue was discovered in Cloud Native Computing Foundation (CNCF) Helm. It displays values of secrets when the --dry-run flag is used. This is a security concern in some use cases, such as a --dry-run call by a CI/CD tool. NOTE: the vendor's position is that this behavior was introduced intentionally, and cannot be removed without breaking backwards compatibility (some users may be relying on these values).

Other sources

An issue was discovered in Cloud Native Computing Foundation (CNCF) Helm through 3.13.3. It displays values of secrets when the --dry-run flag is used. This is a security concern in some use cases, such as a --dry-run call by a CI/CD tool. NOTE: the vendor's position is that this behavior was introduced intentionally, and cannot be removed without breaking backwards compatibility (some users may be relying on these values).

https://github.com/helm/helm/issues/7275 https://www.cncf.io/projects/helm/

Red Hat

An issue was discovered in Cloud Native Computing Foundation (CNCF) Helm through 3.13.3. It displays values of secrets when the --dry-run flag is used. This is a security concern in some use cases, such as a --dry-run call by a CI/CD tool. NOTE: the vendor's position is that this behavior was introduced intentionally, and cannot be removed without breaking backwards compatibility (some users may be relying on these values). Also, it is not the Helm Project's responsibility if a user decides to use --dry-run within a CI/CD environment whose output is visible to unauthorized persons.

MITRE

Affected Software

2 affected components
go/helm.sh/helm/v3>=3.0.0<=3.14.2
Helm helm

Event History

Mar 3, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Advisory Published
via GitHub·09:31 PM
Data Sourced
via GitHub·09:31 PM
DescriptionSeverityWeaknessAffected Software
Mar 6, 2024
Data Sourced
via Red Hat·04:04 PM
DescriptionSeverityAffected Software
Jun 19, 2025
Withdrawn
via GitHub·02:29 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2019-25210?

CVE-2019-25210 is categorized as a medium severity vulnerability.

2

How do I fix CVE-2019-25210?

To fix CVE-2019-25210, upgrade Helm to version 3.14.2 or later.

3

What type of exposure does CVE-2019-25210 present?

CVE-2019-25210 exposes secret values when using the --dry-run flag, which can lead to unintentional information disclosure.

4

Which versions of Helm are affected by CVE-2019-25210?

CVE-2019-25210 affects Helm versions from 3.0.0 to 3.13.3 inclusive.

5

In which scenarios is CVE-2019-25210 particularly concerning?

CVE-2019-25210 is particularly concerning in CI/CD environments where secret values may inadvertently be exposed during dry-run operations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203