CVE-2022-0543

Exp

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.

Published: 2022-02-18 Last update: 2025-11-10 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-0543 is rated Critical Active Threat (100/100): CVSS Critical severity, with high exploitation likelihood (EPSS 94.42%, 100th percentile). CISA KEV confirms active exploitation (added 2022-03-28) affecting Redis / Debian-specific Redis Servers. a weakness (CWE-862) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2022-0543

Name: Debian-specific Redis Server Lua Sandbox Escape Vulnerability · CISA KEV detail

Exploit added: 2022-03-28

Action due: 2022-04-18

Required action: Apply updates per vendor instructions.

Public exploit references (Exploit-DB) for CVE-2022-0543

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-0543

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 94.27% 94.42% +0.15%
2 2025-11-18 94.38% 94.27% -0.11%
3 2025-03-17 — 94.38% —

Full EPSS history (20 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-0543

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
10.0 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 6.0 [email protected]
10.0 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 6.0 134c704f-9b21-4f2e-91b3-4a467353bcc0
10.0 2.0 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 10.0 10.0 [email protected]

Weakness enumeration for CVE-2022-0543

OS Trackers for CVE-2022-0543

vendor priority summary link
debian not yet assigned CVE-2022-0543 not yet assigned priority: Debian including 1 source packages (redis), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-0543
ubuntu medium CVE-2022-0543 medium priority: Ubuntu including 1 source packages (redis), 6 status rows across 6 suites (bionic, focal, impish, trusty, upstream, xenial): not-affected 3, released 3. https://ubuntu.com/security/CVE-2022-0543

Affected software / configurations for CVE-2022-0543

Vendor Product Version Raw CPE
redis redis — cpe:2.3:a:redis:redis:-:*:*:*:*:*:*:*

References for CVE-2022-0543

cvelogic Threat Intelligence