{"answers":{"affected":"4 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-2023-5077 in the wild and no public exploit code.","fix":"Upgrade github.com/hashicorp/vault to 1.13.0 or later.","what":"CVE-2023-5077 is a high-severity missing authorization vulnerability in Hashicorp Vault, published on 28 Sep 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-5077 and fix it if it is affected.\n\nWhat it is: CVE-2023-5077 is a high-severity missing authorization vulnerability in Hashicorp Vault, published on 28 Sep 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-5077 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.13.0\n- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.13.0\n- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.13.0\n- vault (Bitnami): affected from 0.10.0; fixed in 1.13.0\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-2023-5077/ (Markdown: https://insights.sbomify.com/CVE-2023-5077/index.md)","id":"CVE-2023-5077","markdown":"https://insights.sbomify.com/CVE-2023-5077/index.md","name":"CVE-2023-5077","record":{"aliases":["BIT-vault-2023-5077","GHSA-86c6-3g63-5w64","GO-2023-2088"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HashiCorp Vault","requires_auth":"high_privilege","summary":"Attackers can bypass intended IAM restrictions because Vault's Google Cloud engine fails to preserve existing IAM conditions during roleset updates.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HashiCorp","cpe":[{"product":"vault","vendor":"hashicorp"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"The Vault and Vault Enterprise (\"Vault\") Google Cloud secrets engine did not preserve existing Google Cloud IAM Conditions upon creating or updating rolesets. Fixed in Vault 1.13.0.","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":"Vault's Google Cloud Secrets Engine Removed Existing IAM Conditions When Creating / Updating Rolesets","id":"CVE-2023-5077","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"hashicorp:vault","products":["hashicorp:vault"],"type":"missing_authorization","year":"2023"},"n_packages":4,"n_references":1,"next":{"headline":"Security feature bypass in ThinkPad BIOS","id":"CVE-2023-5078"},"packages":[{"ecosystem":"Bitnami","fixed":["1.13.0"],"introduced":["0.10.0"],"last_affected":[],"package":"vault","purl":"pkg:bitnami/vault","source":"BIT-vault-2023-5077"},{"ecosystem":"Go","fixed":["1.13.0"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":null,"source":"GHSA-86c6-3g63-5w64"},{"ecosystem":"Go","fixed":["1.13.0"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":"pkg:golang/github.com/hashicorp/vault","source":"GHSA-86c6-3g63-5w64"},{"ecosystem":"Go","fixed":["1.13.0"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":"pkg:golang/github.com/hashicorp/vault","source":"GO-2023-2088"}],"prev":{"headline":"Ziteboard Online Whiteboard \u003c= 2.9.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via ziteboard Shortcode","id":"CVE-2023-5076"},"products":["Vault","Vault Enterprise"],"published":"2023-09-28","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["HashiCorp"]},"summary":"Attackers can bypass intended IAM restrictions because Vault's Google Cloud engine fails to preserve existing IAM conditions during roleset updates.","url":"https://insights.sbomify.com/CVE-2023-5077/"}