S3Gundo

**Name of the Vulnerable Software and Affected Versions** Apache InLong versions 1.4.0 through 1.8.0 **Description** This issue is related to the deserialization of untrusted data, allowing an attacker to bypass security measures using `t`. The estimated number of potentially affected devices is not provided. There is no information about real-world incidents where this issue was exploited. Technical details about exploitation include the use of `t` to bypass security. No specific API endpoints, vulnerable parameters, or function names are mentioned. **Recommendations** For Apache InLong versions 1.4.0 through 1.8.0, users are advised to upgrade to Apache InLong's 1.9.0 or cherry-pick the solution from the provided GitHub link to solve the issue. As a temporary workaround, consider restricting the deserialization of untrusted data until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Apache Jena versions 3.7.0 through 4.8.0 **Description** The issue is related to insufficient restrictions of called script functions in Apache Jena, allowing a remote user to execute javascript via a SPARQL query. **Recommendations** For Apache Jena versions 3.7.0 through 4.8.0, consider disabling the execution of javascript via SPARQL queries as a temporary workaround until a patch is available. Restrict access to the SPARQL endpoint to minimize the risk of exploitation. Avoid using the vulnerable script functions until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Apache InLong versions 1.1.0 through 1.5.0 **Description** The issue is an Out-of-bounds Read vulnerability in Apache Software Foundation Apache InLong. Users are advised to upgrade to Apache InLong's latest version or cherry-pick a specific patch to solve it. **Recommendations** For Apache InLong versions 1.1.0 through 1.5.0, upgrade to Apache InLong's latest version or cherry-pick https://github.com/apache/inlong/pull/7214 to solve the issue.

**Name of the Vulnerable Software and Affected Versions** Apache InLong versions 1.1.0 through 1.5.0 **Description** The issue is related to the deserialization of untrusted data, which can allow a remote attacker to impact the confidentiality, integrity, and availability of the system. Users are advised to take action to resolve the issue. **Recommendations** For Apache InLong versions 1.1.0 through 1.5.0, upgrade to the latest version of Apache InLong or cherry-pick https://github.com/apache/inlong/pull/7223 to solve the issue.

**Name of the Vulnerable Software and Affected Versions** Apache Linkis versions prior to 1.3.1 **Description** The issue is related to insufficient protection of service data when handling the `allowLoadLocalInfile` parameter with a value of true in the MySQL Connector/J component of Apache Linkis. This could allow a remote attacker to read arbitrary local files by connecting a rogue MySQL server and adding `allowLoadLocalInfile` to true in the JDBC parameter. The parameters in the JDBC URL should be blacklisted to prevent exploitation. **Recommendations** For Apache Linkis versions prior to 1.3.1, upgrade the version of Linkis to version 1.3.1 to resolve the issue. As a temporary workaround, consider blacklisting the parameters in the JDBC URL, specifically the `allowLoadLocalInfile` parameter, to minimize the risk of exploitation. Restrict access to the MySQL Connector/J component to prevent attackers from connecting a rogue MySQL server.

**Name of the Vulnerable Software and Affected Versions** Apache Linkis versions 1.3.0 and earlier **Description** A deserialization vulnerability exists in Apache Linkis when used with the MySQL Connector/J, allowing for possible remote code execution impact. This occurs when an attacker has write access to a database and configures a new datasource with a MySQL data source and malicious parameters. The parameters in the jdbc url should be blacklisted to prevent exploitation. **Recommendations** For Apache Linkis versions 1.3.0 and earlier, upgrade to version 1.3.1 to resolve the issue. As a temporary workaround, consider blacklisting malicious parameters in the jdbc url to minimize the risk of exploitation. Restrict access to the MySQL Connector/J to prevent attackers from configuring new datasources with malicious parameters.