Roberto-Ieru

**Name of the Vulnerable Software and Affected Versions** Lua version 5.4.3 **Description** The issue is related to an erroneous finalizer called during a tail call, leading to a heap-based buffer over-read in Lua 5.4.3. **Recommendations** For Lua version 5.4.3, 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** Lua versions prior to 5.4.4 **Description** An issue in the component luaG runerror of Lua leads to a heap-buffer overflow when a recursive error occurs. **Recommendations** For versions prior to 5.4.4, update to a version that contains a fix for this issue. As a temporary workaround, consider implementing error handling mechanisms to prevent recursive errors that could lead to a heap-buffer overflow.

**Name of the Vulnerable Software and Affected Versions** Lua versions 5.4.0 through 5.4.4 **Description** The issue is related to a heap-based buffer over-read in the `singlevar` function in `lparser.c` of Lua. This might affect systems that compile untrusted Lua code, potentially allowing a remote attacker to execute arbitrary code. The problem is caused by a missing `luaK exp2anyregup` call. **Recommendations** For Lua versions 5.4.0 through 5.4.3, update to version 5.4.4 or later to resolve the issue. For Lua version 5.4.4, although it is mentioned as part of the vulnerable range, the exact fix version is not explicitly stated, but it is implied that updating beyond this version would mitigate the risk. At the moment, there is no information about additional mitigation measures for this specific vulnerability.

**Name of the Vulnerable Software and Affected Versions** Lua versions prior to 5.4.1 **Description** The issue allows a stack redzone cross in `luaO pushvfstring` due to a protection mechanism wrongly calling `luaD callnoyield` twice in a row. **Recommendations** For Lua versions prior to 5.4.1, update to version 5.4.1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Lua versions prior to 5.4.1 **Description** The issue is related to a segmentation fault in the `changedline` function in `ldebug.c`, which can be triggered when `luaG traceexec` is called. This occurs because the code incorrectly assumes that the `oldpc` value is always updated when the flow of control returns to a function. **Recommendations** For Lua versions prior to 5.4.1, update to version 5.4.1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Lua versions prior to 5.4.0 **Description** The issue is related to how Lua handles the interaction between stack resizes and garbage collection, leading to potential heap-based buffer overflow, heap-based buffer over-read, or use-after-free. **Recommendations** For versions prior to 5.4.0, update to version 5.4.0 or later to resolve the issue.