Luajit

Every one of the 6 is a mark on the map. Named now: 1 to 6, most at risk first.

1. LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled.CVE-2020-15890Luajit · 3.1% likely

   CWE-125

2. LuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in lj_err.c.CVE-2020-24372Luajit · 1.5% likely

   CWE-125

3. 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, beca…CVE-2019-19391Luajit · 1.4% likely

   CWE-843

4. LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.CVE-2024-25178Luajit · CVSS 9.1 · 0.7% likely

   CWE-125

5. LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240626 have a stack-buffer-overflow in lj_strfmt_wfnum in lj_strfmt_num.c.CVE-2024-25176Luajit · CVSS 9.8 · 0.6% likely

   CWE-121

6. LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an unsinking of IR_FSTORE for NULL metatable, which leads to Denial of Service (DoS).CVE-2024-25177Luajit · CVSS 7.5 · 0.6% likely

   CWE-476

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.