SQLi via unsanitized sort field in streampark-console <2.1.4
CVE-2023-52290 Published on July 16, 2024

Apache StreamPark (incubating): Unchecked SQL query fields trigger SQL injection vulnerability
In streampark-console the list pages(e.g: application pages), users can sort page by field. This sort field is sent from the front-end to the back-end, and the SQL query is generated using this field. However, because this sort field isn't validated, there is a risk of SQL injection vulnerability. The attacker must successfully log into the system to launch an attack, which may cause data leakage. Since no data will be written, so this is a low-impact vulnerability. Mitigation: all users should upgrade to 2.1.4, Such parameters will be blocked.

Vendor Advisory NVD

Vulnerability Analysis

CVE-2023-52290 is exploitable with network access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have a high impact on confidentiality and integrity, and no impact on availability.

Attack Vector:
NETWORK
Attack Complexity:
LOW
Privileges Required:
LOW
User Interaction:
NONE
Scope:
UNCHANGED
Confidentiality Impact:
HIGH
Integrity Impact:
HIGH
Availability Impact:
NONE

Weakness Type

What is a SQL Injection Vulnerability?

The software 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.

CVE-2023-52290 has been classified to as a SQL Injection vulnerability or weakness.


Products Associated with CVE-2023-52290

Want to know whenever a new CVE is published for Apache Streampark? stack.watch will email you.

 

Affected Versions

Apache Software Foundation Apache StreamPark (incubating): apache streampark:

Exploit Probability

EPSS
0.45%
Percentile
63.06%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.