CVE-2025-13214
BaseFortify
Publication date: 2025-12-11
Last updated on: 2025-12-15
Assigner: IBM Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ibm | aspera_orchestrator | From 4.0.0 (inc) to 4.1.1 (exc) |
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in IBM Aspera Orchestrator versions 4.0.0 through 4.1.0. It allows a remote attacker to send specially crafted SQL statements to the system, which can result in unauthorized viewing, adding, modifying, or deleting of information in the back-end database.
What immediate steps should I take to mitigate this vulnerability?
IBM strongly recommends upgrading IBM Aspera Orchestrator to version 4.1.1 or later to remediate the SQL injection vulnerability present in versions 4.0.0 through 4.1.0. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL injection vulnerability in IBM Aspera Orchestrator versions 4.0.0 through 4.1.0, you should upgrade to IBM Aspera Orchestrator version 4.1.1 or later, as this version addresses related security issues. Applying the latest patches and updates provided by IBM is strongly recommended to remediate this vulnerability. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing an attacker to access or alter sensitive data stored in the back-end database. This could lead to data breaches, loss of data integrity, unauthorized data modification, or deletion, potentially disrupting business operations and compromising confidential information.