CVE-2024-48988
BaseFortify
Publication date: 2025-08-22
Last updated on: 2025-11-04
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | streampark | From 2.1.4 (inc) to 2.1.6 (exc) |
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. |
| CWE-564 | Using Hibernate to execute a dynamic SQL statement built with user-controlled input can allow an attacker to modify the statement's meaning or to execute arbitrary SQL commands. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL Injection issue in Apache StreamPark versions from 2.1.4 before 2.1.6. It exists only in the distribution package using the SpringBoot platform and requires the attacker to have already logged into the platform, meaning the attacker must first bypass authentication. The vulnerability allows an attacker to inject malicious SQL commands, potentially compromising the database.
How can this vulnerability impact me? :
If exploited, this vulnerability can lead to unauthorized access to sensitive data stored in the database (high confidentiality impact), partial modification of data (low integrity impact), and some disruption of availability (low availability impact). However, since exploitation requires prior login, the overall risk is considered relatively low.
What immediate steps should I take to mitigate this vulnerability?
Users are recommended to upgrade Apache StreamPark to version 2.1.6, which fixes the SQL Injection vulnerability. Since the vulnerability requires a successful login to be exploited, ensuring strong authentication controls and monitoring for suspicious login activity can also help mitigate risk.