Tsingshui

**Name of the Vulnerable Software and Affected Versions** DataEase versions prior to 2.10.24 **Description** DataEase is an open source data visualization and analysis tool. The H2 database JDBC URL validation logic can be bypassed using special Unicode characters. This occurs because the case-conversion behavior of these characters differs between the validation process in DataEase and the parsing process in H2. This discrepancy allows attackers to smuggle dangerous parameters, such as `init`, within malicious H2 JDBC connection strings to achieve arbitrary code execution. **Recommendations** Update to version 2.10.24.

Name of the Vulnerable Software and Affected Versions vLLM versions 0.16.0 through 0.18.99 Description vLLM, an inference and serving engine for large language models, contains a server-side request forgery (SSRF) flaw in the `download bytes from url` function. This allows an attacker who can control the batch input JSON to make the vLLM batch runner issue arbitrary HTTP/HTTPS requests from the server, without any URL validation or domain restrictions. The vulnerability resides in the `run batch.py` file, specifically within the `download bytes from url` function, which directly calls `session.get(url)` on a URL provided in the batch input JSON. The `file url` parameter within `BatchTranscriptionRequest` and `BatchTranslationRequest` is vulnerable, as it lacks domain, IP, or port restrictions. This can be exploited to target internal services reachable from the vLLM host. Recommendations Update to vLLM version 0.19.0 or later.

**Name of the Vulnerable Software and Affected Versions** SourceCodester Service Provider Management System version 1.0 **Description** A critical issue has been found in the system, affecting the /classes/Master.php file, specifically when `f=save inquiry`. The manipulation of the `id` argument leads to SQL injection. This issue can be exploited remotely. **Recommendations** For SourceCodester Service Provider Management System version 1.0, consider restricting access to the `Master.php` file, specifically the `save inquiry` function, to minimize the risk of SQL injection attacks until a patch is available. Avoid using the `id` argument in the affected API endpoint until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this issue.