{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-55551 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-55551 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-55551 is a high-severity code injection vulnerability in Exasol JDBC driver, published on 19 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-55551 and fix it if it is affected.\n\nWhat it is: CVE-2024-55551 is a high-severity code injection vulnerability in Exasol JDBC driver, published on 19 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-55551 in the wild and no public exploit code.\n\nAffected product: Exasol JDBC driver. 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-2024-55551/ (Markdown: https://insights.sbomify.com/CVE-2024-55551/index.md)","id":"CVE-2024-55551","markdown":"https://insights.sbomify.com/CVE-2024-55551/index.md","name":"CVE-2024-55551","record":{"aliases":["GHSA-j7qq-8hrp-f3j8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Exasol JDBC driver","requires_auth":"none","summary":"Attackers can achieve remote code execution by injecting malicious parameters into the JDBC URL, triggering JNDI injection in the Exasol JDBC driver.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jdbc_driver","vendor":"exasol"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-471","name":"Modification of Assumed-Immutable Data (MAID)"}],"description":"An issue was discovered in Exasol JDBC driver before 24.2.1 (2024-12-10). Attackers can inject malicious parameters into the JDBC URL, triggering JNDI injection during the process when the JDBC Driver uses this URL to connect to the database. This can further lead to remote code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Code injection in JDBC driver","id":"CVE-2024-55551","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2024-55553"},"packages":[],"prev":{"headline":"Mitel MiCollab Path Traversal","id":"CVE-2024-55550"},"products":["JDBC driver"],"published":"2025-03-19","related":[],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-08-27","vendors":["Exasol"]},"summary":"Attackers can achieve remote code execution by injecting malicious parameters into the JDBC URL, triggering JNDI injection in the Exasol JDBC driver.","url":"https://insights.sbomify.com/CVE-2024-55551/"}