{"answers":{"affected":"1 open source package ship an affected version, including vault. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35192 in the wild and no public exploit code.","fix":"Upgrade vault to 0.11.6 or later.","what":"CVE-2020-35192 is a critical vulnerability in Hashicorp Vault, published on 17 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-35192 and fix it if it is affected.\n\nWhat it is: CVE-2020-35192 is a critical vulnerability in Hashicorp Vault, published on 17 Dec 2020. 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-2020-35192 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vault (Bitnami): affected from 0.6.0; fixed in 0.11.6\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-2020-35192/ (Markdown: https://insights.sbomify.com/CVE-2020-35192/index.md)","id":"CVE-2020-35192","markdown":"https://insights.sbomify.com/CVE-2020-35192/index.md","name":"CVE-2020-35192","record":{"aliases":["BIT-vault-2020-35192","GHSA-9cfc-7fpm-w3g9"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Vault Docker image","requires_auth":"none","summary":"Remote attackers can gain root access to systems using affected Vault Docker images due to a hardcoded blank root password.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vault","vendor":"hashicorp"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"The official vault docker images before 0.11.6 contain a blank password for a root user. System using the vault docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.","ecosystems":["Bitnami"],"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":"Hardcoded credentials in n/a","id":"CVE-2020-35192","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"hashicorp:vault","products":["hashicorp:vault"],"type":"hardcoded_credentials","year":"2020"},"n_packages":1,"n_references":1,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-35193"},"packages":[{"ecosystem":"Bitnami","fixed":["0.11.6"],"introduced":["0.6.0"],"last_affected":[],"package":"vault","purl":"pkg:bitnami/vault","source":"BIT-vault-2020-35192"}],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-35191"},"products":["n/a"],"published":"2020-12-17","related":[{"cvss_score":9.8,"headline":"Improper Input Validation in HashiCorp Vault","id":"CVE-2020-12757","kev_date_added":null,"published":"2020-06-10"},{"cvss_score":9.1,"headline":"Arbitrary Remote Code Execution via Plugin Catalog Abuse","id":"CVE-2025-6000","kev_date_added":null,"published":"2025-08-01"},{"cvss_score":9.1,"headline":"HashiCorp Vault vulnerable to incorrect metadata access","id":"CVE-2022-40186","kev_date_added":null,"published":"2022-09-22"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2022-36129","kev_date_added":null,"published":"2022-07-26"},{"cvss_score":9.1,"headline":"HashiCorp Vault Improper Privilege Management","id":"CVE-2020-10661","kev_date_added":null,"published":"2020-03-23"},{"cvss_score":8.2,"headline":"Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault","id":"CVE-2020-16250","kev_date_added":null,"published":"2020-08-26"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Remote attackers can gain root access to systems using affected Vault Docker images due to a hardcoded blank root password.","url":"https://insights.sbomify.com/CVE-2020-35192/"}