Skip to content
CTI Academy Sponsor CTI Academy
CRITICAL · CVSS 10 CISA Known Exploited Vulnerability

CVE-2022-0543

Debian-specific Redis Server Lua Sandbox Escape Vulnerability

Redis Debian-specific Redis Servers

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.

CVSS
10
CRITICAL
EPSS
99.4%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
18 Feb 2022
CWE-862

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 28 March 2022. US federal agencies were required to remediate it by 18 April 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 99.4%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Frequently asked questions

Is CVE-2022-0543 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2022-0543.

What does CVE-2022-0543 affect?

CVE-2022-0543 affects Redis Debian-specific Redis Servers. 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.

How severe is CVE-2022-0543?

CVE-2022-0543 is rated CRITICAL with a CVSS base score of 10. EPSS puts the probability of exploitation in the next 30 days at 99.4%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 18 April 2022.

How should organisations respond to CVE-2022-0543?

Apply the vendor patch for Redis Debian-specific Redis Servers as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.