Abergmann

The issue is an Out-of-bounds Write vulnerability that allows heap-based buffer over-read or buffer overflow. This can lead to a buffer overflow, which is a type of attack where more data is written to a buffer than it is designed to hold, potentially causing the program to crash or allowing an attacker to execute arbitrary code.

The issue is a Denial of Service in the GitHub repository radareorg/radare2.

The issue allows for Server-side Request Forgery (SSRF) via the "/convert/html" endpoint. This occurs when the `src` attribute of an HTML element, such as an `iframe`, refers to an internal system file, for example, `<iframe src='file:///etc/passwd'>`.

Unauthenticated remote attackers can execute arbitrary code due to insecure usage of the `file get contents()` and `file put contents()` functions. This issue is related to improper code generation management and is exploitable on sites where debug mode is enabled and the Ignition module, which handles error page generation, is active.

The issue allows a NULL pointer dereference in the D-Bus handler for certain `set language` calls.

The issue arises when Envoy logs an incorrect downstream address, considering only the directly connected peer and not the information in the proxy protocol header. This specifically affects situations where tcp-proxy is used as the network filter, excluding HTTP filters.

The issue arises from the failure to prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in `ParseRemoteAddr` in `modules/auth/repo form.go`. This allows for potential exploitation.

The issue is related to out-of-bounds access in the contrib/pmdb2diag/pmdb2diag.c file due to mishandling of the level length.

The issue is related to a command injection vulnerability in the `shutil` module, specifically in the `make archive` function. This vulnerability can be exploited by passing unfiltered user input to the function, potentially resulting in denial of service or information gain via injection of arbitrary files on the system or entire drive. The vulnerability appears to be exploitable via the passage of unfiltered user input to the function.

An issue was discovered where the Docker engine validated a client TLS certificate using both the configured client CA root certificate and all system roots on non-Windows systems. This allowed a client with any domain validated certificate signed by a system-trusted root CA to authenticate.