{"answers":{"affected":"2 open source packages ship an affected version, including net.snowflake:snowflake-jdbc. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-27496 in the wild and no public exploit code.","fix":"Upgrade net.snowflake:snowflake-jdbc to 3.23.1 or later.","what":"CVE-2025-27496 is a low-severity vulnerability in snowflakedb snowflake-jdbc, published on 13 Mar 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-27496 and fix it if it is affected.\n\nWhat it is: CVE-2025-27496 is a low-severity vulnerability in snowflakedb snowflake-jdbc, published on 13 Mar 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-27496 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- net.snowflake:snowflake-jdbc (Maven): affected from 3.0.13; fixed in 3.23.1\n- net.snowflake:snowflake-jdbc (Maven): affected from 3.0.13; fixed in 3.23.1\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-27496/ (Markdown: https://insights.sbomify.com/CVE-2025-27496/index.md)","id":"CVE-2025-27496","markdown":"https://insights.sbomify.com/CVE-2025-27496/index.md","name":"CVE-2025-27496","record":{"aliases":["GHSA-q298-375f-5q63"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Snowflake JDBC driver","requires_auth":"low_privilege","summary":"Attackers with local access can read client-side encryption keys from DEBUG logs in the Snowflake JDBC driver, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"snowflake_jdbc","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":"Snowflake, a platform for using artificial intelligence in the context of cloud computing, has a vulnerability in the Snowflake JDBC driver (\"Driver\") in versions 3.0.13 through 3.23.0 of the driver. When the logging level was set to DEBUG, the Driver 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. Snowflake fixed the issue in version 3.23.1.","ecosystems":["Maven"],"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":"Snowflake JDBC Driver client-side encryption key in DEBUG logs","id":"CVE-2025-27496","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"OpenDJ Denial of Service (Dos) using alias loop","id":"CVE-2025-27497"},"packages":[{"ecosystem":"Maven","fixed":["3.23.1"],"introduced":["3.0.13"],"last_affected":[],"package":"net.snowflake:snowflake-jdbc","purl":null,"source":"GHSA-q298-375f-5q63"},{"ecosystem":"Maven","fixed":["3.23.1"],"introduced":["3.0.13"],"last_affected":[],"package":"net.snowflake:snowflake-jdbc","purl":"pkg:maven/net.snowflake/snowflake-jdbc","source":"GHSA-q298-375f-5q63"}],"prev":{"headline":"SQL injection in TeleControl Server Basic","id":"CVE-2025-27495"},"products":["snowflake-jdbc"],"published":"2025-03-13","related":[{"cvss_score":7.8,"headline":"Snowflake JDBC allows an untrusted search path on Windows","id":"CVE-2025-24789","kev_date_added":null,"published":"2025-01-29"},{"cvss_score":7.3,"headline":"Snowflake JDBC vulnerable to command injection via SSO URL authentication","id":"CVE-2023-30535","kev_date_added":null,"published":"2023-04-14"},{"cvss_score":5.9,"headline":"Snowflake JDBC Security Advisory","id":"CVE-2024-43382","kev_date_added":null,"published":"2024-10-30"},{"cvss_score":4.8,"headline":"snowflakedb snowflake-jdbc JDBC URL SdkProxyRoutePlanner.java SdkProxyRoutePlanner redos","id":"CVE-2026-3293","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":4.4,"headline":"Snowflake JDBC uses insecure temporary credential cache file permissions","id":"CVE-2025-24790","kev_date_added":null,"published":"2025-01-29"}],"sources":[{"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":"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-03-13","vendors":["snowflakedb"]},"summary":"Attackers with local access can read client-side encryption keys from DEBUG logs in the Snowflake JDBC driver, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2025-27496/"}