{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19786 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19786 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19786 is a high-severity vulnerability in Hashicorp Vault, published on 5 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-19786 and fix it if it is affected.\n\nWhat it is: CVE-2018-19786 is a high-severity vulnerability in Hashicorp Vault, published on 5 Dec 2018. 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-2018-19786 in the wild and no public exploit code.\n\nAffected product: Hashicorp Vault. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2018-19786/ (Markdown: https://insights.sbomify.com/CVE-2018-19786/index.md)","id":"CVE-2018-19786","markdown":"https://insights.sbomify.com/CVE-2018-19786/index.md","name":"CVE-2018-19786","record":{"aliases":["GHSA-5jfh-x25r-v632"],"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":"HashiCorp Vault may leak the master key to server logs during specific misconfigured autoseal failures, exposing sensitive cryptographic material.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vault","vendor":"hashicorp"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"HashiCorp Vault before 1.0.0 writes the master key to the server log in certain unusual or misconfigured scenarios in which incorrect data comes from the autoseal mechanism without an error being reported.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2018-19786","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"hashicorp:vault","products":["hashicorp:vault"],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Neutralization of Input During Web Page Generation in LXML","id":"CVE-2018-19787"},"packages":[],"prev":{"headline":"XSS in PHP-Proxy-App through v3.0","id":"CVE-2018-19785"},"products":["n/a"],"published":"2018-12-05","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":"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-05","vendors":["n/a"]},"summary":"HashiCorp Vault may leak the master key to server logs during specific misconfigured autoseal failures, exposing sensitive cryptographic material.","url":"https://insights.sbomify.com/CVE-2018-19786/"}