CVE-2022-0543
CRITICALCVE-2022-0543 is a critical-severity (CVSS 10) CWE-862 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-03-28) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-03-28. Federal agencies were required to remediate by 2022-04-18.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2022-0543.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-0543 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
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.
Affected Products
redisredisResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
It was discovered, that redis, a persistent key-value database, due to a…
It was discovered, that redis, a persistent key-value database, due to a…
It was discovered, that redis, a persistent key-value database, due to a…
It was discovered, that redis, a persistent key-value database, due to a…
It was discovered, that redis, a persistent key-value database, due to a…
It was discovered, that redis, a persistent key-value database, due to a…
It was discovered, that redis, a persistent key-value database, due to a…
It was discovered, that redis, a persistent key-value database, due to a…
It was discovered, that redis, a persistent key-value database, due to a…
It was discovered, that redis, a persistent key-value database, due to a…
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2022-0543 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is CVE-2022-0543 in your dependencies?
Find it across , including transitive dependencies.