Databricks JDBC Driver up to 2.6.39 JNDI krbJAASFile injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in Databricks JDBC Driver up to 2.6.39. This affects an unknown part of the component JNDI Handler. Performing a manipulation of the argument krbJAASFile results in injection. This vulnerability is reported as CVE-2024-49194. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Databricks JDBC Driver up to 2.6.39. It has been classified as critical. This affects an unknown functionality of the component JNDI Handler. The manipulation of the argument krbJAASFile with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Databricks JDBC Driver 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.

It is possible to read the advisory at kb.databricks.com. This vulnerability is uniquely identified as CVE-2024-49194 since 10/13/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1055 according to MITRE ATT&CK.

Upgrading to version 2.6.40 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-3598). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Hardware Driver Software

Vendor

• Databricks

Name

• JDBC Driver

Version

• 2.6.0
• 2.6.1
• 2.6.2
• 2.6.3
• 2.6.4
• 2.6.5
• 2.6.6
• 2.6.7
• 2.6.8
• 2.6.9
• 2.6.10
• 2.6.11
• 2.6.12
• 2.6.13
• 2.6.14
• 2.6.15
• 2.6.16
• 2.6.17
• 2.6.18
• 2.6.19
• 2.6.20
• 2.6.21
• 2.6.22
• 2.6.23
• 2.6.24
• 2.6.25
• 2.6.26
• 2.6.27
• 2.6.28
• 2.6.29
• 2.6.30
• 2.6.31
• 2.6.32
• 2.6.33
• 2.6.34
• 2.6.35
• 2.6.36
• 2.6.37
• 2.6.38
• 2.6.39

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion