Skip to content

Apache Linkis Metadata Query Service JDBC: JDBC Datasource Module with Mysql has file read vulnerability

Moderate severity GitHub Reviewed Published Jan 14, 2025 to the GitHub Advisory Database • Updated Jan 14, 2025

Package

maven org.apache.linkis:linkis-metadata-query-service-jdbc (Maven)

Affected versions

>= 1.5.0, < 1.7.0

Patched versions

1.7.0

Description

Affected versions:

  • Apache Linkis Metadata Query Service JDBC 1.5.0 before 1.7.0

Description:

In Apache Linkis <1.7.0, due to the lack of effective filtering of parameters, an attacker configuring malicious Mysql JDBC parameters in the DataSource Manager Module will allow the attacker to read arbitrary files from the Linkis server. Therefore, the parameters in the Mysql JDBC URL should be blacklisted. This attack requires the attacker to obtain an authorized account from Linkis before it can be carried out. Versions of Apache Linkis < 1.6.0 will be affected.

We recommend users upgrade the version of Linkis to version 1.7.0.

References

Published by the National Vulnerability Database Jan 14, 2025
Published to the GitHub Advisory Database Jan 14, 2025
Reviewed Jan 14, 2025
Last updated Jan 14, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Weaknesses

CVE ID

CVE-2024-45627

GHSA ID

GHSA-8cvq-3jjp-ph9p

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.