CVE-2025-0966
BaseFortify
Publication date: 2025-06-25
Last updated on: 2025-07-08
Assigner: IBM Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| ibm | infosphere_information_server | From 11.7 (inc) to 11.7.1 (exc) |
| ibm | aix | * |
| microsoft | windows | * |
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 issue in IBM InfoSphere Information Server 11.7. A remote attacker can send specially crafted SQL statements to the server, which could allow them to view, add, modify, or delete data in the back-end database without authorization. It is classified under CWE-89 and affects versions 11.7.0.0 through 11.7.1.6. [1]
How can this vulnerability impact me? :
The vulnerability can allow an attacker to remotely access and manipulate sensitive data in the back-end database, potentially leading to unauthorized disclosure, data modification, or deletion. This can compromise the confidentiality, integrity, and availability of your data, with a high impact on confidentiality and lower impacts on integrity and availability. [1]
What immediate steps should I take to mitigate this vulnerability?
Apply updates to IBM InfoSphere Information Server versions 11.7.1.0 or 11.7.1.6 and apply the security patch for InfoSphere DataStage. Note that no workarounds or mitigations are currently available, so patching is the recommended immediate step. [1]