{"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-2024-43382 in the wild and no public exploit code.","fix":"Upgrade net.snowflake:snowflake-jdbc to 3.20.0 or later.","what":"CVE-2024-43382 is a medium-severity vulnerability in n/a, published on 30 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-43382 and fix it if it is affected.\n\nWhat it is: CVE-2024-43382 is a medium-severity vulnerability in n/a, published on 30 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-43382 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- net.snowflake:snowflake-jdbc (Maven): affected from 3.2.6; fixed in 3.20.0\n- net.snowflake:snowflake-jdbc (Maven): affected from 3.2.6; fixed in 3.20.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-43382/ (Markdown: https://insights.sbomify.com/CVE-2024-43382/index.md)","id":"CVE-2024-43382","markdown":"https://insights.sbomify.com/CVE-2024-43382/index.md","name":"CVE-2024-43382","record":{"aliases":["GHSA-f686-hw9c-xw9c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Snowflake JDBC driver","requires_auth":"high_privilege","summary":"The Snowflake JDBC driver fails to apply client-side encryption to uploaded data, potentially exposing sensitive information to unauthorized readers.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"snowflake_jdbc","vendor":"snowflake"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"Snowflake JDBC driver versions \u003e= 3.2.6 and \u003c= 3.19.1 have an Incorrect Security Setting that can result in data being uploaded to an encrypted stage without the additional layer of protection provided by client side encryption.","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 Security Advisory","id":"CVE-2024-43382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"Apache Lucene.Net.Replicator: Remote Code Execution in Lucene.Net.Replicator","id":"CVE-2024-43383"},"packages":[{"ecosystem":"Maven","fixed":["3.20.0"],"introduced":["3.2.6"],"last_affected":[],"package":"net.snowflake:snowflake-jdbc","purl":null,"source":"GHSA-f686-hw9c-xw9c"},{"ecosystem":"Maven","fixed":["3.20.0"],"introduced":["3.2.6"],"last_affected":[],"package":"net.snowflake:snowflake-jdbc","purl":"pkg:maven/net.snowflake/snowflake-jdbc","source":"GHSA-f686-hw9c-xw9c"}],"prev":{"headline":"reNgine vulnerable to Stored Cross-Site Scripting (XSS) via DNS Record Poisoning","id":"CVE-2024-43381"},"products":["n/a"],"published":"2024-10-30","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":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"},{"cvss_score":3.3,"headline":"Snowflake JDBC Driver client-side encryption key in DEBUG logs","id":"CVE-2025-27496","kev_date_added":null,"published":"2025-03-13"}],"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":"total"},"state":"PUBLISHED","updated":"2024-10-31","vendors":["n/a"]},"summary":"The Snowflake JDBC driver fails to apply client-side encryption to uploaded data, potentially exposing sensitive information to unauthorized readers.","url":"https://insights.sbomify.com/CVE-2024-43382/"}