L0Ne1Y

An incorrect default permissions issue exists in Apache DolphinScheduler.

An authenticated user can execute any shell script on the server through the alert script functionality due to improper input validation.

Name of the Vulnerable Software and Affected Versions: Apache Druid versions prior to 30.0.1 Description: The issue allows users with certain permissions to bypass restrictions on JDBC connections, potentially reading data from other database systems. This is possible by crafting a specific JDBC connection string when configuring a MySQL connection, allowing users to provide properties not on the allowed list. The functionality in question is used for setting up Druid lookups or running ingestion tasks. Users without the permission to configure JDBC connections cannot exploit this issue. Recommendations: For versions prior to 30.0.1, update to Apache Druid 30.0.1 to resolve the issue. As a temporary workaround, consider restricting the configuration of JDBC connections to trusted administrators only, and ensure that the allowed properties list is carefully reviewed and restricted to necessary properties.

The issue is related to an authentication bypass vulnerability in Apache HugeGraph-Server, which can be exploited by remote attackers to execute arbitrary code. This vulnerability is caused by the exploitation of assumed-immutable data.

The issue is related to improper input validation, allowing an authenticated user to execute arbitrary, unsandboxed javascript on the server. This can potentially lead to remote code execution.

A Server-Side Request Forgery (SSRF) issue affects Apache IoTDB Workbench, allowing an attacker to access the local network. This issue only affects products that are no longer supported by the maintainer.

The issue arises when a user's session is not invalidated after logout. Upon successful login, the Backend service returns an "Authorization" credential, which can still be used to initiate requests and access data even after the user has logged out.

The issue allows a regular user to view everyone's user flink information, including executeSQL and config, after successfully logging in. This is achieved by manually making a request using the authorization token.

The issue allows a user to perform a template injection attack, resulting in Remote Code Execution on the server. This can be done after a successful login, making it a moderate-impact issue.

A Server-Side Request Forgery (SSRF) issue exists in Apache StreamPipes during the installation process of pipeline elements. The software allowed users to configure custom endpoints for installing additional pipeline elements, but these endpoints were not properly validated. This allowed an attacker to get StreamPipes to send an HTTP GET request to an arbitrary address.

The issue allows a user to obtain sensitive information, including usernames, passwords, and salt values of other users, after a successful login. This is due to the Backend service returning "Authorization" as the front-end authentication credential.

The issue is related to an Unrestricted Upload of File with dangerous type vulnerability in Apache StreamPipes. This vulnerability may allow the upload of executable files, potentially leading to remote code execution (RCE). The unrestricted upload is only possible for authenticated and authorized users.

Name of the Vulnerable Software and Affected Versions: Apache StreamPark versions prior to 2.1.4 Description: The issue is related to incorrect handling of the ` character in the Project Module of Apache StreamPark, allowing remote attackers to execute arbitrary commands. The vulnerability can be exploited if an attacker has system-level permissions and is logged in to the StreamPark system. The risk level of this vulnerability is considered low, as it typically requires authorization to log in to the system and users would not manually input dangerous operation commands. Recommendations: For versions prior to 2.1.4, upgrade to version 2.1.4 to resolve the issue. As a temporary workaround, consider restricting access to the Project module or limiting the use of the ` character in build arguments to minimize the risk of exploitation.

The issue is related to insufficient input validation in the Core component of Oracle WebLogic Server, allowing an unauthenticated attacker with network access via T3 or IIOP to compromise the server. Successful attacks can result in the takeover of Oracle WebLogic Server.

Name of the Vulnerable Software and Affected Versions: Apache Linkis versions <=1.5.0 Description: The issue is related to the lack of effective filtering of parameters in the DataSource Manager Module of Apache Linkis. This allows an attacker to configure malicious `db2` parameters, resulting in jndi injection. The attack requires the attacker to obtain an authorized account from Linkis before it can be carried out. Recommendations: For Apache Linkis versions <=1.5.0, upgrade the version of Linkis to version 1.6.0. As a temporary workaround, consider blacklisting the parameters in the DB2 URL to minimize the risk of exploitation. Restrict access to the DataSource Manager Module to authorized accounts only.

The issue is related to an SQL Injection vulnerability due to improper neutralization of special elements used in an SQL command. This affects products that are no longer supported by the maintainer. Users are advised to find an alternative or restrict access to the instance to trusted users.

The issue is related to an Improper Authentication vulnerability in Apache Submarine Commons Utils. If the user doesn't explicitly set `submarine.auth.default.secret`, a default value will be used. This vulnerability only affects products that are no longer supported by the maintainer. As the project is retired, no fix will be released.

The issue is related to an Incorrect Authorization vulnerability in Apache Submarine Server Core. This vulnerability only affects products that are no longer supported by the maintainer. Users are recommended to find an alternative or restrict access to the instance to trusted users.

The issue is related to the deserialization of untrusted data, allowing attackers to bypass security using malicious parameters.

The issue exists due to insufficient validation of user-input data in the UriComponentsBuilder component of the Spring Framework. This can allow a remote attacker to perform a Server-Side Request Forgery (SSRF) attack. Applications that use UriComponentsBuilder to parse externally provided URLs and perform validation checks on the host are affected.