Threats / Redis / CVE-2022-0543
CVE-2022-0543
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Redis Debian-specific Servers vulnerability
Redis Debian-specific Lua sandbox escape vulnerability allows remote code execution through improper sandbox isolation in Lua script execution.
Verdict
Today item — known-exploited.
A Lua sandbox escape in Debian-specific Redis servers enables unauthenticated remote code execution. The vulnerability has been actively exploited in the wild with high EPSS score, posing critical risk to affected deployments.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
19 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-28).
Probability (EPSS)
EPSS 0.9967 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Redis, Debian-specific Redis Servers. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-862 Missing Authorization — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious Lua script that breaks out of the sandbox restrictions specific to Debian Redis builds.
Business
Attacker gains arbitrary code execution on the Redis server with the privileges of the Redis process.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute system commands through the escaped Lua environment to establish persistence or pivot to other systems.
Business
Infrastructure is compromised, enabling data theft, lateral movement, or further system compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I access sensitive data stored in Redis or connected systems, or deploy malware across the infrastructure.
Business
Confidentiality and integrity of critical data and systems are breached, with potential regulatory and reputational damage.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05