{"answers":{"affected":"2 open source packages ship an affected version, including com.databricks:databricks-jdbc.","exploited":"There is no known exploitation of CVE-2024-49194 in the wild and no public exploit code.","fix":"Upgrade com.databricks:databricks-jdbc to 2.6.40 or later.","what":"CVE-2024-49194 is a high-severity code injection vulnerability in n/a, published on 17 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-49194 and fix it if it is affected.\n\nWhat it is: CVE-2024-49194 is a high-severity code injection vulnerability in n/a, published on 17 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-49194 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.databricks:databricks-jdbc (Maven): affected from 2.0; fixed in 2.6.40\n- com.databricks:databricks-jdbc (Maven): affected from 2.0; fixed in 2.6.40\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-49194/ (Markdown: https://insights.sbomify.com/CVE-2024-49194/index.md)","id":"CVE-2024-49194","markdown":"https://insights.sbomify.com/CVE-2024-49194/index.md","name":"CVE-2024-49194","record":{"aliases":["GHSA-jxw2-jvxf-5vrp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Databricks JDBC Driver","requires_auth":"low_privilege","summary":"An attacker can achieve remote code execution by tricking a victim into using a crafted JDBC connection URL with a malicious krbJAASFile parameter.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"Databricks JDBC Driver 2.x before 2.6.40 could potentially allow remote code execution (RCE) by triggering a JNDI injection via a JDBC URL parameter. The vulnerability is rooted in the improper handling of the krbJAASFile parameter. An attacker could potentially exploit this vulnerability to achieve Remote Code Execution in the context of the driver by tricking a victim into using a crafted connection URL that uses the property krbJAASFile.","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":"Databricks JDBC Driver Command Injection vulnerability","id":"CVE-2024-49194","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-49195"},"packages":[{"ecosystem":"Maven","fixed":["2.6.40"],"introduced":["2.0"],"last_affected":[],"package":"com.databricks:databricks-jdbc","purl":null,"source":"GHSA-jxw2-jvxf-5vrp"},{"ecosystem":"Maven","fixed":["2.6.40"],"introduced":["2.0"],"last_affected":[],"package":"com.databricks:databricks-jdbc","purl":"pkg:maven/com.databricks/databricks-jdbc","source":"GHSA-jxw2-jvxf-5vrp"}],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2024-49193"},"products":["n/a"],"published":"2024-12-17","related":[],"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":"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":"2025-07-02","vendors":["n/a"]},"summary":"An attacker can achieve remote code execution by tricking a victim into using a crafted JDBC connection URL with a malicious krbJAASFile parameter.","url":"https://insights.sbomify.com/CVE-2024-49194/"}