{"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-2024-2660 in the wild and no public exploit code.","fix":"Upgrade github.com/hashicorp/vault to 1.16.0 or later.","what":"CVE-2024-2660 is a medium-severity vulnerability in Hashicorp Vault, published on 4 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-2660 and fix it if it is affected.\n\nWhat it is: CVE-2024-2660 is a medium-severity vulnerability in Hashicorp Vault, published on 4 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-2660 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.16.0\n- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.16.0\n- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.16.0\n- vault (Bitnami): affected from 1.14.0; fixed in 1.16.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-2024-2660/ (Markdown: https://insights.sbomify.com/CVE-2024-2660/index.md)","id":"CVE-2024-2660","markdown":"https://insights.sbomify.com/CVE-2024-2660/index.md","name":"CVE-2024-2660","record":{"aliases":["BIT-vault-2024-2660","GHSA-j2rp-gmqv-frhv","GO-2024-2690","openSUSE-SU-2024:14104-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"HashiCorp Vault","requires_auth":"high_privilege","summary":"Attackers can bypass TLS certificate authentication by exploiting improper OCSP response validation in HashiCorp Vault.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HashiCorp","cpe":[{"product":"vault","vendor":"hashicorp"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-636","name":"Not Failing Securely"}],"description":"Vault and Vault Enterprise TLS certificates auth method did not correctly validate OCSP responses when one or more OCSP sources were configured. This vulnerability, CVE-2024-2660, affects Vault and Vault Enterprise 1.14.0 and above, and is fixed in Vault 1.16.0 and Vault Enterprise 1.16.1, 1.15.7, and 1.14.11.","ecosystems":["Bitnami","Go","openSUSE:Tumbleweed"],"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 TLS Cert Auth Method Did Not Correctly Validate OCSP Responses","id":"CVE-2024-2660","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"hashicorp:vault","products":["hashicorp:vault"],"type":"security_feature_bypass","year":"2024"},"n_packages":5,"n_references":1,"next":{"headline":"Barcode Scanner with Inventory \u0026 Order Manager \u003c= 1.5.4 - Authenticated (Subscriber+) SQL Injection","id":"CVE-2024-2661"},"packages":[{"ecosystem":"Bitnami","fixed":["1.16.0"],"introduced":["1.14.0"],"last_affected":[],"package":"vault","purl":"pkg:bitnami/vault","source":"BIT-vault-2024-2660"},{"ecosystem":"Go","fixed":["1.16.0"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":null,"source":"GHSA-j2rp-gmqv-frhv"},{"ecosystem":"Go","fixed":["1.16.0"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":"pkg:golang/github.com/hashicorp/vault","source":"GHSA-j2rp-gmqv-frhv"},{"ecosystem":"Go","fixed":["1.16.0"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":"pkg:golang/github.com/hashicorp/vault","source":"GO-2024-2690"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["3.9.0-1.1"],"introduced":["0"],"last_affected":[],"package":"sops","purl":"pkg:rpm/opensuse/sops\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:14104-1"}],"prev":{"headline":"Command injection in SMM, SMM2, FPC","id":"CVE-2024-2659"},"products":["Vault","Vault Enterprise"],"published":"2024-04-04","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":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":"partial"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["HashiCorp"]},"summary":"Attackers can bypass TLS certificate authentication by exploiting improper OCSP response validation in HashiCorp Vault.","url":"https://insights.sbomify.com/CVE-2024-2660/"}