First published: Tue Apr 11 2023(Updated: )
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.5.0. By manipulating the "orderType" parameter and the ordering of the returned content using an SQL injection attack, an attacker can extract the username of the user with ID 1 from the "user" table, one character at a time. Users are advised to upgrade to Apache InLong's 1.6.0 or cherry-pick [1] to solve it. https://programmer.help/blogs/jdbc-deserialization-vulnerability-learning.html [1] https://github.com/apache/inlong/issues/7529 https://github.com/apache/inlong/issues/7529
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache InLong | =1.4.0 | |
Apache InLong | =1.5.0 | |
maven/org.apache.inlong:manager-service | >=1.4.0<1.6.0 | 1.6.0 |
maven/org.apache.inlong:manager-pojo | >=1.4.0<1.6.0 | 1.6.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2023-30465.
This vulnerability affects Apache InLong versions 1.4.0 through 1.5.0.
The severity of CVE-2023-30465 is medium with a CVSS score of 5.3.
This vulnerability is an SQL injection vulnerability in Apache InLong, which can be exploited by manipulating the 'orderType' parameter and the ordering of the returned content using an SQL command.
To mitigate CVE-2023-30465, it is recommended to update Apache InLong to version 1.5.1 or later, which contains a fix for this vulnerability.