CVE-2024-55551: An issue was discovered in Exasol JDBC driver before 24.2.1 (2024-12-10)
CVE-2024-55551 is a high-severity flaw (CVSS 8.3) affecting jdbc driver. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.3 (High) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.6% (top 50%) |
| CISA exploited list | No |
| Weakness | CWE-471 |
| Published | 2025-03-19 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2024-55551?
jdbc driver: upgrade to 24.2.1. Exact commands for each OS are on this page.
Is CVE-2024-55551 being exploited?
CVE-2024-55551 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2024-55551 affect?
CVE-2024-55551 affects jdbc driver. Severity is high (CVSS 8.3). 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 databas
How urgent is CVE-2024-55551?
Priority 42/100. High severity