Vulnerability in lua5.1 (UBUNTU-CVE-2025-49844)
Summary
Vulnerability in lua5.1 (UBUNTU-CVE-2025-49844). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2:2.8.4-2ubuntu0.2+esm5 or later.
Original description
The description as published by the source.
Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.
Source: OSV.dev (Open Source Vulnerabilities) OSV
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 UBUNTU-CVE-2025-49844 has been found in lua5.1.
Successful exploitation can lead to full system takeover.
What to do: upgrade lua5.1 to 2:2.8.4-2ubuntu0.2+esm5 or later.
If unsure, ask your IT team or search "lua5.1 UBUNTU-CVE-2025-49844" on the vendor's site.
UBUNTU-CVE-2025-49844 (lua5.1)
Attack vector: remote (network-reachable) / no user interaction
Patched: 2:2.8.4-2ubuntu0.2+esm5 — 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 lua5.1.
Check the vendor advisory for the affected versions of lua5.1.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2:2.8.4-2ubuntu0.2+esm5.
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 'lua5.1' . 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
-
1Identify exposure identify
grep -r 'lua5.1' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
lua5.1を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade lua5.1 to 2:2.8.4-2ubuntu0.2+esm5ステージング環境で 2:2.8.4-2ubuntu0.2+esm5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report github.com
- report github.com
- report github.com
- report github.com