{"answers":{"affected":"6 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35177 in the wild and no public exploit code.","fix":"Upgrade github.com/hashicorp/vault to a fixed version for your release line: 1.5.6 or 1.6.1.","what":"CVE-2020-35177 is a medium-severity 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-35177 and fix it if it is affected.\n\nWhat it is: CVE-2020-35177 is a medium-severity 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-35177 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/hashicorp/vault (Go): affected from 1.5.0; fixed in 1.5.6, 1.6.1\n- github.com/hashicorp/vault (Go): affected from 1.5.0; fixed in 1.5.6\n- github.com/hashicorp/vault (Go): affected from 1.5.0; fixed in 1.5.6\n- github.com/hashicorp/vault (Go): affected from 1.6.0; fixed in 1.6.1\n- github.com/hashicorp/vault (Go): affected from 1.6.0; fixed in 1.6.1\n- vault (Bitnami): affected from 1.5.0; fixed in 1.5.6, 1.6.1\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-35177/ (Markdown: https://insights.sbomify.com/CVE-2020-35177/index.md)","id":"CVE-2020-35177","markdown":"https://insights.sbomify.com/CVE-2020-35177/index.md","name":"CVE-2020-35177","record":{"aliases":["BIT-vault-2020-35177","GHSA-rpgp-9hmg-j25x","GO-2024-2508"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"HashiCorp Vault","requires_auth":"none","summary":"Attackers can enumerate users via the LDAP auth method in HashiCorp Vault, exposing valid account names.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vault","vendor":"hashicorp"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"HashiCorp Vault and Vault Enterprise 1.4.1 and newer allowed the enumeration of users via the LDAP auth method. Fixed in 1.5.6 and 1.6.1.","ecosystems":["Bitnami","Go"],"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":"Enumeration of users in HashiCorp Vault","id":"CVE-2020-35177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"hashicorp:vault","products":["hashicorp:vault"],"type":"information_disclosure","year":"2020"},"n_packages":6,"n_references":2,"next":{"headline":"The official composer docker images before 1.8.3 contain a blank password for a root user.","id":"CVE-2020-35184"},"packages":[{"ecosystem":"Bitnami","fixed":["1.5.6","1.6.1"],"introduced":["1.5.0","1.6.0"],"last_affected":[],"package":"vault","purl":"pkg:bitnami/vault","source":"BIT-vault-2020-35177"},{"ecosystem":"Go","fixed":["1.5.6","1.6.1"],"introduced":["1.5.0","1.6.0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":"pkg:golang/github.com/hashicorp/vault","source":"GO-2024-2508"},{"ecosystem":"Go","fixed":["1.5.6"],"introduced":["1.5.0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":null,"source":"GHSA-rpgp-9hmg-j25x"},{"ecosystem":"Go","fixed":["1.5.6"],"introduced":["1.5.0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":"pkg:golang/github.com/hashicorp/vault","source":"GHSA-rpgp-9hmg-j25x"},{"ecosystem":"Go","fixed":["1.6.1"],"introduced":["1.6.0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":null,"source":"GHSA-rpgp-9hmg-j25x"},{"ecosystem":"Go","fixed":["1.6.1"],"introduced":["1.6.0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":"pkg:golang/github.com/hashicorp/vault","source":"GHSA-rpgp-9hmg-j25x"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2020-35176"},"products":["n/a"],"published":"2020-12-17","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-35192","kev_date_added":null,"published":"2020-12-17"},{"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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":"Attackers can enumerate users via the LDAP auth method in HashiCorp Vault, exposing valid account names.","url":"https://insights.sbomify.com/CVE-2020-35177/"}