CVE-2025-29847
BaseFortify
Publication date: 2026-01-19
Last updated on: 2026-01-27
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | linkis | From 1.3.0 (inc) to 1.8.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Apache Linkis occurs when the JDBC engine and data source functionality use a URL parameter on the frontend that has been encoded multiple times. This multiple URL encoding can bypass the system's checks, allowing unauthorized access to system files through JDBC parameters.
How can this vulnerability impact me? :
The vulnerability can allow unauthorized users to access system files via JDBC parameters, potentially exposing sensitive data or system information, which could lead to further exploitation or compromise of the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves checking if the connection information used in the JDBC engine contains the '%' character, which indicates URL encoding that may bypass system checks. You can monitor or log JDBC connection URLs and inspect them for multiple rounds of URL encoding (presence of '%' characters). Specific commands are not provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include continuously checking if the connection information contains the '%' character and performing URL decoding if it does. The recommended solution is to upgrade Apache Linkis to version 1.8.0, which fixes the issue.