Lua 5.3.5 has a use-after-free in lua_upvaluejoin in lapi.c. For example, a crash outcome might be achieved by an attacker who is able to trigger a debug.upvaluejoin call in which the arguments have certain relationships.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| http://packetstormsecurity.com/files/151335/Lua-5.3.5-Use-After-Free.html | exploit vdb entry third party advisory |
| https://github.com/Lua-Project/cve-analysis/blob/a43c9ccd00274b31fa2f24c6c8f20ce36655682d/CVE-2019-6706.pdf | third party advisory exploit |
| https://github.com/lua/lua/commit/89aee84cbc9224f638f3b7951b306d2ee8ecb71e | third party advisory patch |
| http://lua-users.org/lists/lua-l/2019-01/msg00039.html | broken link |
| https://access.redhat.com/security/cve/cve-2019-6706 | third party advisory |
| https://lists.debian.org/debian-lts-announce/2023/06/msg00031.html | mailing list |