{"answers":{"affected":"1 open source package ship an affected version, including vault. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-2877 in the wild and no public exploit code.","fix":"Upgrade vault to 1.15.8 or later.","what":"CVE-2024-2877 is a medium-severity vulnerability in Hashicorp Vault, published on 30 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-2877 and fix it if it is affected.\n\nWhat it is: CVE-2024-2877 is a medium-severity vulnerability in Hashicorp Vault, published on 30 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-2877 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vault (Bitnami): affected from 1.15.0; fixed in 1.15.8\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-2877/ (Markdown: https://insights.sbomify.com/CVE-2024-2877/index.md)","id":"CVE-2024-2877","markdown":"https://insights.sbomify.com/CVE-2024-2877/index.md","name":"CVE-2024-2877","record":{"aliases":["BIT-vault-2024-2877","GHSA-vxc5-78f8-rhp4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Vault Enterprise","requires_auth":"high_privilege","summary":"Attackers with audit log access can read sensitive HTTP headers from performance standby nodes in Vault Enterprise deployments.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HashiCorp","cpe":[{"product":"vault","vendor":"hashicorp"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Vault Enterprise, when configured with performance standby nodes and a configured audit device, will inadvertently log request headers on the standby node. These logs may have included sensitive HTTP request information in cleartext.\n\nThis vulnerability, CVE-2024-2877, was fixed in Vault Enterprise 1.15.8.","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":"Vault Enterprise Leaks Sensitive HTTP Request Headers in the Audit Log When Deployed With a Performance Standby Node","id":"CVE-2024-2877","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"hashicorp:vault","products":["hashicorp:vault"],"type":"information_disclosure","year":"2024"},"n_packages":1,"n_references":2,"next":{"headline":"Allocation of Resources Without Limits or Throttling in GitLab","id":"CVE-2024-2878"},"packages":[{"ecosystem":"Bitnami","fixed":["1.15.8"],"introduced":["1.15.0"],"last_affected":[],"package":"vault","purl":"pkg:bitnami/vault","source":"BIT-vault-2024-2877"}],"prev":{"headline":"SQL injection in Email Subscribers \u0026 Newsletters – Email Marketing, Post Notifications \u0026 Newsletter Plugin for WordPress","id":"CVE-2024-2876"},"products":["Vault Enterprise"],"published":"2024-04-30","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":"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":"2025-02-13","vendors":["HashiCorp"]},"summary":"Attackers with audit log access can read sensitive HTTP headers from performance standby nodes in Vault Enterprise deployments.","url":"https://insights.sbomify.com/CVE-2024-2877/"}