Approved changes feed: RSS · Atom
cpe:2.3:a:moonjit_project:moonjit:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Moonjit Project (9682d561-0bf0-50d9-bb67-b919a36bec8f) |
|---|---|
| Product | Moonjit (67a97d53-d861-508d-bb79-0c4a00a4f989) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/luajit/luajit |
purl2cpe | 2026-06-01 10:12:32.806700 |
pkg:github/moonjit/moonjit |
purl2cpe | 2026-06-01 10:12:32.806703 |
pkg:rpm/opensuse/moonjit |
purl2cpe | 2026-06-01 10:12:32.806706 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-19391 |
vulnerable | 2026-06-08 05:13:22.243129 |
Details available
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
Published: 2019-11-29T15:18:49.000Z
Updated: 2025-11-03T18:07:53.427Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.