Lucene search
K

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

🗓️ 30 Jun 2024 14:00:00Reported by MicrosoftType 
mscve
 mscve
🔗 msrc.microsoft.com👁 2 Views

LuaJIT debug.getinfo type confusion enables arbitrary memory read or write due to mishandled stack levels and options.

Related
Detection

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

30 Jun 2024 14:00Current
7.8High risk
Vulners AI Score7.8
CVSS 26.4
CVSS 3.19.1
EPSS0.00209
SSVC
2