Ali Raza

An integer wraparound exists in the `Handle 0x38 RequestFileTransfer()` function. This allows unauthenticated attackers to bypass the file path length check by sending a short RequestFileTransfer (SID 0x38) request with the `filePathAndNameLength` variable set between 0xFFFC and 0xFFFF. This can lead to callbacks reading past the receive buffer, resulting in target crashes or memory disclosure.

An integer underflow exists in the container box parser. On 32-bit platforms, 64-bit box sizes are truncated to `size t`, allowing remote attackers to provide a specially crafted JPEG XL file. This causes the decoder to interpret attacker-controlled codestream bytes as phantom box headers, which enables the injection of arbitrary metadata, such as Exif, XMP, IPTC, and JUMBF, and may lead to out-of-bounds reads.

PythonTools in libs/agno/agno/tools/python.py contains a path traversal issue. This occurs when parent-directory traversal sequences are supplied in the `file name` argument passed to the `read file()`, `save to file()`, or `run python file()` tool actions. Attackers can use direct tool invocation or prompt injection in agent-processed content to bypass the `base dir` boundary. This allows for arbitrary file read, arbitrary file write, or arbitrary Python code execution with the privileges of the process user.

Name of the Vulnerable Software and Affected Versions libcap (affected versions not specified) Description A flaw exists in libcap where a local unprivileged user can exploit a Time-of-check-to-time-of-use (TOCTOU) race condition in the `cap set file()` function. This allows an attacker with write access to a parent directory to redirect file capability updates to a file controlled by the attacker. Capabilities can be injected into or stripped from unintended executables, potentially leading to privilege escalation. Recommendations At the moment, there is no information about a newer version that contains a fix for this vulnerability.

The issue is related to a heap-based buffer overflow in the zlog library, specifically in the `zlog rule new()` function. This occurs because the size of `record name` is limited to `MAXLEN PATH(1024) + 1`, but `file path` can contain data up to `MAXLEN CFG LINE(MAXLEN PATH*4) + 1`, leading to a missing check when copying `record name` from `file path + 1`. This can cause a buffer overflow, allowing an attacker to potentially overwrite the `zlog record fn` `record func` function pointer, resulting in arbitrary code execution or remote code execution (RCE).