CVE-2024-10553: Jdbc Deserialization in h2oai/h2o-3
A vulnerability in the h2oai/h2o-3 REST API versions 3.46.0.4 allows unauthenticated remote attackers to execute arbitrary code via deserialization of untrusted data. The vulnerability exists in the endpoints POST /99/ImportSQLTable and POST /3/SaveToHiveTable, where user-controlled JDBC URLs are passed to DriverManager.getConnection, leading to deserialization if a MySQL or PostgreSQL driver is available in the classpath. This issue is fixed in version 3.46.0.6.
Other sources
A vulnerability in the h2oai/h2o-3 REST API versions 3.46.0.4 allows unauthenticated remote attackers to execute arbitrary code via deserialization of untrusted data. The vulnerability exists in the endpoints POST /99/ImportSQLTable and POST /3/SaveToHiveTable, where user-controlled JDBC URLs are passed to DriverManager.getConnection, leading to deserialization if a MySQL or PostgreSQL driver is available in the classpath. This issue is fixed in version 3.47.0.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-10553?
CVE-2024-10553 is classified as a high severity vulnerability due to its potential for remote code execution.
How do I fix CVE-2024-10553?
To fix CVE-2024-10553, upgrade h2o-3 to version 3.47.0 or later, which contains the necessary patches.
What are the affected versions for CVE-2024-10553?
CVE-2024-10553 affects h2o-3 versions prior to 3.47.0.
Can CVE-2024-10553 be exploited remotely?
Yes, CVE-2024-10553 can be exploited remotely by unauthenticated attackers.
What API endpoints are vulnerable in CVE-2024-10553?
The vulnerable API endpoints in CVE-2024-10553 are POST /99/ImportSQLTable and POST /3/SaveToHiveTable.