Redis Lua Use-After-Free may lead to remote code execution

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• redis redisbefore 6.2.20
• redis redis7.0 and later · before 7.2.11
• redis redis7.4.0 and later · before 7.4.6
• redis redis8.0.0 and later · before 8.0.4
• redis redis8.2.0 and later · before 8.2.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

• redis redis

  • < 8.2.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2022-0543It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific) Lua sandbox escapeKEV
  100Now
• CVE-2023-36824Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis
  58Plan
• CVE-2022-24834Heap overflow issue with the Lua cjson library used by Redis
  47Plan
• CVE-2023-22458Integer overflow in multiple Redis commands can lead to denial-of-service
  44Plan
• CVE-2024-46981Redis' Lua library commands may lead to remote code execution
  41Plan
• CVE-2022-36021Redis string pattern matching can be abused to achieve Denial of Service
  40Plan

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1free(dev->buf);2/* ... another thread is still running ... */3process(dev->buf);

1lock(&dev->lock);2free(dev->buf);3dev->buf = NULL;4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.