3 results (0.011 seconds)

CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 1

LuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in lj_err.c. LuaJIT versiones hasta 2.1.0-beta3, presenta una lectura fuera de límites en la función lj_err_run en el archivo lj_err.c. • https://github.com/LuaJIT/LuaJIT/issues/603 • CWE-125: Out-of-bounds Read •

CVSS: 7.5EPSS: 0%CPEs: 6EXPL: 1

LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled. LuaJit versiones hasta 2.1.0-beta3, presenta una lectura fuera de límites, porque el salto de trama del manejador __gc es manejado inapropiadamente • https://github.com/LuaJIT/LuaJIT/issues/601 https://lists.debian.org/debian-lts-announce/2020/07/msg00026.html https://usn.ubuntu.com/4501-1 • CWE-125: Out-of-bounds Read •

CVSS: 9.1EPSS: 0%CPEs: 2EXPL: 0

In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a type confusion issue that leads to arbitrary memory write or read operations, because certain cases involving valid stack levels and > options are mishandled. NOTE: The LuaJIT project owner states that the debug libary is unsafe by definition and that this is not a vulnerability. When LuaJIT was originally developed, the expectation was that the entire debug library had no security guarantees and thus it made no sense to assign CVEs. However, not all users of later LuaJIT derivatives share this perspective ** EN DISPUTA ** En LuaJIT hasta la versión 2.0.5, como se usaba en Moonjit antes de 2.1.2 y otros productos, debug.getinfo tiene un problema de confusión de tipos que conduce a operaciones arbitrarias de escritura o lectura de memoria, porque ciertos casos involucran niveles de pila válidos y > las opciones se manejan mal. NOTA: El propietario del proyecto LuaJIT declara que la biblioteca de depuración no es segura por definición y que esto no es una vulnerabilidad. • https://github.com/LuaJIT/LuaJIT/pull/526 • CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') •