{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-46329 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-46329 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46329 is a low-severity vulnerability in snowflakedb libsnowflakeclient, published on 29 Apr 2025. 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-2025-46329 and fix it if it is affected.\n\nWhat it is: CVE-2025-46329 is a low-severity vulnerability in snowflakedb libsnowflakeclient, published on 29 Apr 2025. 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-2025-46329 in the wild and no public exploit code.\n\nAffected product: snowflakedb libsnowflakeclient. 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-2025-46329/ (Markdown: https://insights.sbomify.com/CVE-2025-46329/index.md)","id":"CVE-2025-46329","markdown":"https://insights.sbomify.com/CVE-2025-46329/index.md","name":"CVE-2025-46329","record":{"aliases":["GHSA-jx4f-645p-wjpx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Snowflake C/C++ connector","requires_auth":"low_privilege","summary":"Attackers with local access can read sensitive encryption keys from debug logs in the Snowflake C/C++ connector.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"connector_for_c\\/c\\+\\+","vendor":"snowflake"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"libsnowflakeclient is the Snowflake Connector for C/C++. Versions starting from 0.5.0 to before 2.2.0, are vulnerable to local logging of sensitive information. When the logging level was set to DEBUG, the Connector would log locally the client-side encryption master key of the target stage during the execution of GET/PUT commands. This key by itself does not grant access to any sensitive data without additional access authorizations, and is not logged server-side by Snowflake. This issue has been patched in version 2.2.0.","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":"Snowflake Connector for C/C++ inserts client-side encryption key in DEBUG logs","id":"CVE-2025-46329","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Snowflake Connector for C/C++ retries malformed requests","id":"CVE-2025-46330"},"packages":[],"prev":{"headline":"NodeJS Driver for Snowflake has race condition when checking access to Easy Logging configuration file","id":"CVE-2025-46328"},"products":["libsnowflakeclient"],"published":"2025-04-29","related":[{"cvss_score":3.3,"headline":"Snowflake Connector for C/C++ retries malformed requests","id":"CVE-2025-46330","kev_date_added":null,"published":"2025-04-29"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-29","vendors":["snowflakedb"]},"summary":"Attackers with local access can read sensitive encryption keys from debug logs in the Snowflake C/C++ connector.","url":"https://insights.sbomify.com/CVE-2025-46329/"}