Skip to content
Fencer Intel
low 3.9

CVE-2022-24735 json

Lua scripts can be manipulated to overcome ACL rules in Redis

published 4y ago modified 2mo ago also BIT-keydb-2022-24735 , BIT-redis-2022-24735 , BIT-valkey-2022-24735 , EUVD-2022-29582 , GHSA-647m-2wmq-qmvq

cvss
3.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

Redis is an in-memory database that persists on disk. By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis prior to version 7.0.0 or 6.2.7 can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. The Lua script execution environment in Redis provides some measures that prevent a script from creating side effects that persist and can affect the execution of the same, or different script, at a later time. Several weaknesses of these measures have been publicly known for a long time, but they had no security impact as the Redis security model did not endorse the concept of users or privileges. With the introduction of ACLs in Redis 6.0, these weaknesses can be exploited by a less privileged users to inject Lua code that will execute at a later time, when a privileged user executes a Lua script. The problem is fixed in Redis versions 7.0.0 and 6.2.7. An additional workaround to mitigate this problem without patching the redis-server executable, if Lua scripting is not being used, is to block access to `SCRIPT LOAD` and `EVAL` commands using ACL rules.

Patch / fix

  • bitnami keydb 6.2.7
  • bitnami redis 6.2.7
  • bitnami valkey 6.2.7
  • redis redis 6.2.7
  • redis Debian 14, Debian 13, Debian 12 5:7.0.1-4

debian advisories DEBIAN-CVE-2022-24735

  • redis RHEL 8 6.2.7-1.module+el8.7.0+15197+cc495aeb
  • redis RHEL 9 6.2.7-1.el9

red hat advisories RHSA-2022:7541RHSA-2022:8096

  • redis SLE Module for Server Applications 15 SP4, openSUSE Leap 15.4 6.2.6-150400.3.3.7
  • redis SLE Module for Server Applications 15 SP3, openSUSE Leap 15.3 6.0.14-150200.6.11.1

suse advisories SUSE-SU-2022:1929-1SUSE-SU-2022:1842-1

  • redis openSUSE Tumbleweed 6.2.7-1.1

opensuse advisories openSUSE-SU-2024:12030-1

  • redis AlmaLinux 9 6.2.7-1.el9
  • redis AlmaLinux 8 6.2.7-1.module_el8.7.0+3288+a82c1b48

almalinux advisories ALSA-2022:8096ALSA-2022:7541

  • redis Rocky Linux 9 6.2.7-1.el9
  • redis Rocky Linux 8 6.2.7-1.module+el8.7.0+1105+8815ce78

rocky linux advisories RLSA-2022:8096RLSA-2022:7541

  • redis Alpine 3.24, Alpine 3.23, Alpine 3.22 +8 more 6.2.7-r0

alpine advisories ALPINE-CVE-2022-24735

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • redis CBL-Mariner 2.0 6.2.7-1

azure linux advisories AZL-9598

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2022-24735 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-24735 updated cvss 3.9

redis: Code injection via Lua script execution environment

  • Red Hat 3scale API Management Platform 2 redis Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/search-api-rhel8, rhacm2/redisgraph-tls-rhel8 Red Hat Ansible Automation Platform 1.2 redis Red Hat Ansible Tower 3 redis Red Hat Enterprise Linux 8 redis Red Hat Fuse 7 io.hawt-hawtio-integration io.hawt-hawtio-integration
    affected: workaround, no fix available “If Lua scripting is not being used, this vulnerability can be mitigated by blocking access to SCRIPT LOAD and EVAL commands using ACL rules.”
  • Red Hat OpenStack Platform 13 (Queens) redis
    affected: workaround, no fix planned “If Lua scripting is not being used, this vulnerability can be mitigated by blocking access to SCRIPT LOAD and EVAL commands using ACL rules.”
  • Red Hat Software Collections rh-redis5-redis, rh-redis6-redis
    affected: workaround, no fix available “If Lua scripting is not being used, this vulnerability can be mitigated by blocking access to SCRIPT LOAD and EVAL commands using ACL rules.”
  • Red Hat Enterprise Linux AppStream (v. 8) redis 6.2.7-1.module+el8.7.0+15197+cc495aeb
    fixed: vendor fix “If Lua scripting is not being used, this vulnerability can be mitigated by blocking access to SCRIPT LOAD and EVAL commands using ACL rules.” RHSA-2022:7541
  • Red Hat Enterprise Linux AppStream (v. 9) redis 6.2.7-1.el9
    fixed: vendor fix “If Lua scripting is not being used, this vulnerability can be mitigated by blocking access to SCRIPT LOAD and EVAL commands using ACL rules.” RHSA-2022:8096

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

2.25% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/redis/redis/pull/10651 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 3.9 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
OSV 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami keydb
<6.2.7
6.2.7
bitnami redis
<6.2.7
6.2.7
bitnami valkey
<6.2.7
6.2.7

Affected products

  • redis redis

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of redis/redis published their own advisory on GitHub. Reviewed sources take precedence over it.