# CVE-2022-0543: Debian-specific Redis Server Lua Sandbox Escape

> A Debian-specific packaging issue in Redis allows attackers to escape the Lua sandbox and execute arbitrary code remotely.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 28 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Feb 2022
- **Updated:** 21 Oct 2025
- **Also known as:** BIT-redis-2022-0543, DEBIAN-CVE-2022-0543, DSA-5081-1, GHSA-9wpj-h5jq-88p9, MINI-2548-6x3j-m4rj, MINI-3358-fff2-24q5, MINI-53vf-pf36-p7q7, MINI-9rcq-pp58-hxxq, MINI-gjcc-8c66-x7p3, MINI-j566-xx65-hhwh, MINI-p5hh-7xxm-gc53, MINI-pxc2-p9hp-qpmv, MINI-vvxx-gh4m-rr8m, UBUNTU-CVE-2022-0543, USN-5316-1

## What is CVE-2022-0543?

CVE-2022-0543 is a critical code injection vulnerability in Debian redis, published on 18 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific) Lua sandbox escape, which could result in remote code execution.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-0543?

1 open source package ship an affected version, including redis. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redis` | Bitnami | All versions | None |

Products: Redis Redis.

## How do I fix CVE-2022-0543?

Apply the vendor's patch. US federal agencies must fix it by 18 Apr 2022.

## Is CVE-2022-0543 being exploited?

Yes. Attackers have exploited CVE-2022-0543 in the wild since at least 28 Mar 2022.

Public exploit code:

- CVE-2022-0543_RCE,Redis Lua沙盒绕过 命令执行 (github_poc): https://github.com/0x7eTeam/CVE-2022-0543
- Redis 沙盒逃逸（CVE-2022-0543）POC&EXP (github_poc): https://github.com/z92g/CVE-2022-0543
- redis未授权、redis_CVE-2022-0543检测利用二合一脚本 (github_poc): https://github.com/SiennaSkies/redisHack
- Redis RCE through Lua Sandbox Escape vulnerability (github_poc): https://github.com/fulxey/CVE-2022-0543
- Redis Lua Sandbox Escape (metasploit)
- CVE-2022-0543 - Redis RCE Vulnerability home lab for Red Teaming, Penetration Testing Training with just one DOCKER (github_poc): https://github.com/netw0rk7/CVE-2022-0543-Home-Lab

## Other vulnerabilities in Debian redis

- [CVE-2026-23479](https://insights.sbomify.com/CVE-2026-23479/): redis-server use-after-free in unblock client flow may allow remote code execution (high 7.7)
- [CVE-2026-25243](https://insights.sbomify.com/CVE-2026-25243/): redis-server RESTORE invalid memory access may allow remote code execution (high 7.7)
- [CVE-2025-62507](https://insights.sbomify.com/CVE-2025-62507/): Redis: Bug in XACKDEL may lead to stack overflow and potential RCE (high 7.7)
- [CVE-2025-48367](https://insights.sbomify.com/CVE-2025-48367/): Redis DoS Vulnerability due to bad connection error handling (high 7.5)
- [CVE-2023-31655](https://insights.sbomify.com/CVE-2023-31655/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0543 and fix it if it is affected.

What it is: CVE-2022-0543 is a critical code injection vulnerability in Debian redis, published on 18 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-0543 in the wild since at least 28 Mar 2022.

Affected packages and fixed versions:
- redis (Bitnami): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0543/ (Markdown: https://insights.sbomify.com/CVE-2022-0543/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0543
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0543
- OSV: https://osv.dev/vulnerability/CVE-2022-0543

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0543/
Summaries are generated and may contain mistakes; the official description above is the record.