L2Yyd5

An issue exists where the `MediaFilter` Guice mapping in `WebModule.java` and the Jetty `ResourceServlet` in `WebServer.java` interpret path parameters differently at the '/api/media/*' endpoint. An unauthenticated attacker can bypass session and device authorization checks by inserting a semicolon at the Servlet boundary if they know or guess a device unique ID and media filename. This occurs because Jetty dispatches the noncanonical path to the `ResourceServlet`, allowing read-only disclosure of protected media files such as photographs, audio, or video. Reverse proxies that reject or rewrite semicolon path parameters may block these requests.

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.

DataEase is an open source data visualization analysis tool. Versions 2.10.19 and below exhibit inconsistent locale handling between the JDBC URL validation logic and the H2 JDBC engine's internal parsing. DataEase uses `String.toUpperCase()` without specifying an explicit locale, relying on the JVM's default runtime locale for security checks, while H2 JDBC normalizes URLs using `Locale.ENGLISH`. In Turkish locale environments (tr TR), Java converts the lowercase letter 'i' to 'İ' (dotted capital I) instead of 'I', allowing a malicious parameter like `iNIT` to bypass DataEase's blacklist while H2 correctly interprets it as `INIT`. This discrepancy enables attackers to smuggle dangerous JDBC parameters past DataEase's security validation. The issue has been confirmed as exploitable in real-world DataEase deployments running under affected regional settings.