Vulnerability in luajit
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2019-19391 has been found in luajit.
Confidential information can be exposed externally.
What to do: upgrade luajit to 2.1.0~beta3+git20210112+dfsg-2 or later.
If unsure, ask your IT team or search "luajit DEBIAN-CVE-2019-19391" on the vendor's site.
DEBIAN-CVE-2019-19391 (luajit)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.1.0~beta3+git20210112+dfsg-2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in luajit.
Check the vendor advisory for the affected versions of luajit.
Severity: ?. Confidential information can be exposed externally.
Update to 2.1.0~beta3+git20210112+dfsg-2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'luajit' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'luajit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
luajitを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade luajit to 2.1.0~beta3+git20210112+dfsg-2ステージング環境で 2.1.0~beta3+git20210112+dfsg-2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | luajit |
< 2.1.0~beta3+git20210112+dfsg-2 |
2.1.0~beta3+git20210112+dfsg-2 |
| Debian:13 | luajit |
< 2.1.0~beta3+git20210112+dfsg-2 |
2.1.0~beta3+git20210112+dfsg-2 |
| Debian:14 | luajit |
< 2.1.0~beta3+git20210112+dfsg-2 |
2.1.0~beta3+git20210112+dfsg-2 |
Original description The description as published by the source.
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
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org