Ali Raza

**Name of the Vulnerable Software and Affected Versions** libjxl versions prior to 0.12 **Description** 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. **Recommendations** Update libjxl to version 0.12 or later.

**Name of the Vulnerable Software and Affected Versions** Agno (affected versions not specified) **Description** 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. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability. As a temporary workaround, restrict the use of the `file name` argument in the `read file()`, `save to file()`, and `run python file()` functions to prevent the use of traversal sequences.

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.

**Name of the Vulnerable Software and Affected Versions** zlog versions 1.1.0 through 1.2.17 **Description** 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). **Recommendations** For zlog versions 1.1.0 through 1.2.17, as a temporary workaround, consider disabling the `zlog rule new()` function until a patch is available. Restrict access to the `zlog rule s` class to minimize the risk of exploitation. Avoid using overly long strings for user-defined outputs in configuration files to prevent buffer overflow. At the moment, there is no information about a newer version that contains a fix for this vulnerability.