{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-25210 in the wild and no public exploit code.","fix":"No fix published yet.","what":"CVE-2019-25210 is a critical vulnerability in n/a, published on 3 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-25210 and fix it if it is affected.\n\nWhat it is: CVE-2019-25210 is a critical vulnerability in n/a, published on 3 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-25210 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-25210/ (Markdown: https://insights.sbomify.com/CVE-2019-25210/index.md)","id":"CVE-2019-25210","markdown":"https://insights.sbomify.com/CVE-2019-25210/index.md","name":"CVE-2019-25210","record":{"aliases":["CLEANSTART-2026-HT81402","MINI-6962-26wg-4xwc","MINI-f4jp-29q5-wrwm","MINI-fx69-4wcq-4mmq","MINI-fxqv-g53h-979x","MINI-jw83-wc62-2w9j","MINI-m9jf-h43j-x9vw"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Helm CLI tool","requires_auth":"none","summary":"Helm CLI exposes secret values in output when using the --dry-run flag, potentially leaking sensitive data in CI/CD logs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"helm","vendor":"helm"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2019-25210","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Gin mishandles a wildcard at the end of an origin string","id":"CVE-2019-25211"},"packages":[],"prev":{"headline":"** REJECT ** DO NOT USE THIS CVE RECORD.","id":"CVE-2019-25209"},"products":["n/a"],"published":"2024-03-03","related":[{"cvss_score":9.8,"headline":"Helm Unsafe Link Following","id":"CVE-2019-18658","kev_date_added":null,"published":"2019-11-12"},{"cvss_score":9.8,"headline":"Helm Improper Certificate Validation","id":"CVE-2019-1010275","kev_date_added":null,"published":"2019-07-17"},{"cvss_score":8.5,"headline":"Helm Chart Dependency Updating With Malicious Chart.yaml Content And Symlink Can Lead To Code Execution","id":"CVE-2025-53547","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":8.5,"headline":"lookup Function Information Discolosure in Helm","id":"CVE-2020-11013","kev_date_added":null,"published":"2020-04-24"},{"cvss_score":8.4,"headline":"Helm has a path traversal in plugin metadata version enables arbitrary file write outside Helm plugin directory","id":"CVE-2026-35204","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":8.4,"headline":"Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin install","id":"CVE-2026-35205","kev_date_added":null,"published":"2026-04-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-04","vendors":["n/a"]},"summary":"Helm CLI exposes secret values in output when using the --dry-run flag, potentially leaking sensitive data in CI/CD logs.","url":"https://insights.sbomify.com/CVE-2019-25210/"}