CVE-2024-55551
Exasol Jdbc Driver remote code execution
- Published19 Mar 2025
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:HAffected products
Remediation
References
- https://docs.exasol.com/db/7.1/release_notes_drivers_jdbc/24.2.1.htm
- https://docs.exasol.com/db/latest/connect_exasol/drivers/jdbc.htm
- https://gist.github.com/azraelxuemo/9565ec9219e0c3e9afd5474904c39d0f
- https://www.blackhat.com/eu-24/briefings/schedule/index.html#a-novel-attack-surface-java-authentication-and-authorization-service-jaas-42179
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-55551 being actively exploited?
CVE-2024-55551 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.64%.
How severe is CVE-2024-55551?
CVE-2024-55551 has a CVSS 3.1 base score of 8.3, rated high. EPSS estimates a 0.64% probability of exploitation.
Which products are affected by CVE-2024-55551?
Affected products include Exasol Jdbc Driver.
How do I fix CVE-2024-55551?
Upgrade affected software to a fixed version, for example Exasol Jdbc Driver 24.2.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-55551 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.