CVE-2024-46981
Public on
Last Modified:
Description
A flaw was found in the Redis server. This flaw allows an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, potentially leading to remote code execution.
Statement
The problem exists in all versions of Redis with Lua scripting.
This vulnerability in Redis is classified as high severity rather than moderate due to its potential impact and exploitation scope. By manipulating the Lua garbage collector through crafted scripts, an authenticated attacker can achieve remote code execution (RCE), allowing them to execute arbitrary commands on the host system. This compromises not only the integrity and confidentiality of the data stored in Redis but also the underlying server itself. Furthermore, the exploitation does not require direct access to the server binary, making it feasible for attackers to execute through legitimate, albeit malicious, commands.
Mitigation
A workaround to mitigate the problem without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.
Additional Information
- This content is not included.Bugzilla 2336004: redis: Redis' Lua library commands may lead to remote code execution
- Content from cwe.mitre.org is not included.CWE-416: Use After Free
- FAQ: Frequently asked questions about CVE-2024-46981
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2024-46981
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2024-46981
Content from github.com is not included.https://github.com/redis/redis/releases/tag/6.2.17
Content from github.com is not included.https://github.com/redis/redis/releases/tag/7.2.7
Content from github.com is not included.https://github.com/redis/redis/releases/tag/7.4.2
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| Discovery 1 for RHEL 9 | discovery/discovery-server-rhel9 | Fixed | RHSA-2025:1249 |
| Discovery 1 for RHEL 9 | discovery/discovery-ui-rhel9 | Fixed | RHSA-2025:1249 |
| OpenShift Lightspeed | openshift-lightspeed-tech-preview/lightspeed-service-api-rhel9 | Affected | |
| Red Hat Ansible Automation Platform 1.2 | ansible-tower | Not affected | |
| Red Hat Enterprise Linux 8 | redis:6 | Fixed | RHSA-2025:0595 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | redis:6 | Fixed | RHSA-2025:0685 |
| Red Hat Enterprise Linux 8.4 Telecommunications Update Service | redis:6 | Fixed | RHSA-2025:0685 |
| Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions | redis:6 | Fixed | RHSA-2025:0685 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | redis:6 | Fixed | RHSA-2025:0689 |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | redis:6 | Fixed | RHSA-2025:0689 |
| Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions | redis:6 | Fixed | RHSA-2025:0689 |
| Red Hat Enterprise Linux 8.8 Extended Update Support | redis:6 | Fixed | RHSA-2025:0640 |
| Red Hat Enterprise Linux 9 | redis:7 | Fixed | RHSA-2025:0692 |
| Red Hat Enterprise Linux 9 | redis | Fixed | RHSA-2025:0693 |
| Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions | redis | Fixed | RHSA-2025:0400 |
| Red Hat Enterprise Linux 9.2 Extended Update Support | redis | Fixed | RHSA-2025:0398 |
| Red Hat Enterprise Linux 9.4 Extended Update Support | redis | Fixed | RHSA-2025:0399 |
| Red Hat Enterprise Linux 9.4 Extended Update Support | redis:7 | Fixed | RHSA-2025:0566 |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/bootc-amd-rhel9 | Will not fix | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/bootc-azure-amd-rhel9 | Will not fix | |
| Red Hat Enterprise Linux AI (RHEL AI) | rhelai1/instructlab-amd-rhel9 | Will not fix | |
| Red Hat Fuse 7 | io.hawt-hawtio-integration | Not affected | |
| Red Hat Quay 3 | quay/quay-rhel8 | Affected |
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
| CVSS v3 Score Breakdown | Red Hat | NVD |
|---|---|---|
| CVSS v3 Base Score | 7 | 9.8 |
| Attack Vector | Local | Network |
| Attack Complexity | High | Low |
| Privileges Required | Low | None |
| User Interaction | None | None |
| Scope | Unchanged | Unchanged |
| Confidentiality Impact | High | High |
| Integrity Impact | High | High |
| Availability Impact | High | High |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
My product is listed as "Out of Support Scope". What does this mean?
Not sure what something means? Check out our Security Glossary.