Lalalala5678

The `Context.Scheme` function unconditionally trusts forwarded scheme headers from any client. This allows a client connecting via plaintext HTTP to claim an HTTPS scheme, bypassing the HTTPSRedirect mechanism by making the request appear secure. Additionally, when used behind a TLS-terminating proxy that forwards attacker-controlled headers, a claimed HTTP scheme can suppress the Strict-Transport-Security header, even if the browser receives the response over HTTPS. This occurs because the framework lacks a trusted-source configuration for these headers.

An improper authentication issue in the Apache Doris Frontend (FE) meta service allows an unauthenticated remote attacker to access internal metadata service endpoints. The affected endpoints rely on client-supplied node information for authentication without sufficiently verifying the requesting party. In specific network configurations, this allows an attacker to bypass access controls and access internal FE metadata interfaces, which may expose sensitive cluster information.

Sanic's core HTTP/1.1 parser fails to fully consume the `trailer-part` after the terminating zero chunk before reusing the keep-alive connection buffer. A remote unauthenticated client can place attacker-controlled bytes in this trailer region, which Sanic then parses and routes as a hidden second request following the initial outer request. This failure in request-boundary integrity can enable request smuggling when Sanic is deployed behind intermediaries such as reverse proxies, gateways, or caches.

A path traversal issue exists in the local proxy containment guard. The system employs plain string prefix comparison without validating path separators, allowing attackers to access sibling directories that start with the repository directory name. This can lead to unauthorized reading, writing, or deleting of files outside the intended repository root.

An authorization bypass exists in the Calendar Block. The function `action get events()` fails to verify the `canView` permission on the calendar, which allows the disclosure of restricted event details.