BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2024-46981High confidence

Redis' Lua library commands may lead to remote code execution

redis · redis

Official source article: GitHub GHSA-39H2-X6C4-6W4C ↗. Check the applicable product and release in the original source.

7.0HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 8.17% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs redis redis and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

20 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communityredictVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.3.2-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · communityredisVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.2.7-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · mainvalkeyVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.2.8-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · communityredictVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.3.2-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communityredisVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.2.7-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · mainvalkeyVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.2.8-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · communityredictVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.3.2-r0Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · communityredisVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.2.7-r0Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · mainvalkeyVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.2.8-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourceredisVendor fix publishedDebian records a fixed source-package version for this release.5:7.0.15-3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · sourcevalkeyVendor fix publishedDebian records a fixed source-package version for this release.8.0.2+dfsg1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceredisVendor fix publishedDebian records a fixed source-package version for this release.5:7.0.15-1~deb12u3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceredictVendor fix publishedDebian records a fixed source-package version for this release.7.3.2+ds-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceredisVendor fix publishedDebian records a fixed source-package version for this release.5:7.0.15-3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcevalkeyVendor fix publishedDebian records a fixed source-package version for this release.8.0.2+dfsg1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceredictVendor fix publishedDebian records a fixed source-package version for this release.7.3.2+ds-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceredisVendor fix publishedDebian records a fixed source-package version for this release.5:7.0.15-3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcevalkeyVendor fix publishedDebian records a fixed source-package version for this release.8.0.2+dfsg1-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveredisVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.5:7.0.15-1ubuntu0.24.04.1Canonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivevalkeyVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.7.2.8+dfsg1-0ubuntu0.24.04.2Canonical Ubuntu Security ↗Source updated 6 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-42220

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

Redis is an open source, in-memory database that persists on disk. An authenticated user may use a specially crafted Lua script to manipulate the garbage collector and potentially lead to remote code execution. The problem is fixed in 7.4.2, 7.2.7, and 6.2.17. An additional 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.

What

Redis is an open source, in-memory database that persists on disk. An authenticated user may use a specially crafted Lua script to manipulate the garbage collector and potentially lead to remote code execution. The problem is fixed in 7.4.2, 7.2.7, and 6.2.17. An additional 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.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

What

Redis is an open source, in-memory database that persists on disk. An authenticated user may use a specially crafted Lua script to manipulate the garbage collector and potentially lead to remote code execution. The problem is fixed in 7.4.2, 7.2.7, and 6.2.17. An additional 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.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
local access → Use After Free → execute code or commands in the affected security context
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
Remote code executionCWE-416Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0017Redis: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Redis ausnutzen, um beliebigen Programmcode auszuführen oder einen Denial of Service zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250108Security Bulletin 08 Jan 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 08 Jan 2025, published on 8 January 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1125Multiples vulnérabilités dans les produits VMware

in de sécurité VMware 38353 du 04 septembre 2026 https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38353 Bulletin de sécurité VMware 38354 du 04 septembre 2026 https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38354 Référence CVE CVE-2024-11053 https://www.cve.org/CVERecord?id=CVE-2024-11053 Référence CVE CVE-2024-31227 https://www.cve.org/CVERecord?id=CVE-2024-31227 Référence CVE CVE-2024-31228 https://www.cve.org/CVERecord?id=CVE-2024-31228 Référence CVE CVE-2024-31449 https://www.cve.org/CVERecord?id=CVE-2024-31449 Référence CVE CVE-2024-46981 https://www.cve.org/CVERecord?id=CVE-2024-46981 Référence CVE CVE-2024-51741 https://www.cve.org/CVERecord?id=CVE-2024-51741 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-13034 https://www.cve.org/CVERecord?id=CVE-2025-13034 Référence CVE CVE-2025-14017 https://www.cve.org/CVERecord?id=CVE-2025-14017 Référence CVE CVE-2025-14524 https://www.cve.org/CVERecord?id=CVE-2025-14524 Référence CVE CVE-2025-15079 https://www.cve.org/CVERecord?id=CVE-2025-15079 Référence CVE CVE-2025-15224 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0524Multiples vulnérabilités dans VMware Tanzu

Record?id=CVE-2024-3596 Référence CVE CVE-2024-3651 https://www.cve.org/CVERecord?id=CVE-2024-3651 Référence CVE CVE-2024-38949 https://www.cve.org/CVERecord?id=CVE-2024-38949 Référence CVE CVE-2024-38950 https://www.cve.org/CVERecord?id=CVE-2024-38950 Référence CVE CVE-2024-41996 https://www.cve.org/CVERecord?id=CVE-2024-41996 Référence CVE CVE-2024-45336 https://www.cve.org/CVERecord?id=CVE-2024-45336 Référence CVE CVE-2024-45341 https://www.cve.org/CVERecord?id=CVE-2024-45341 Référence CVE CVE-2024-45993 https://www.cve.org/CVERecord?id=CVE-2024-45993 Référence CVE CVE-2024-4603 https://www.cve.org/CVERecord?id=CVE-2024-4603 Référence CVE CVE-2024-46981 https://www.cve.org/CVERecord?id=CVE-2024-46981 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-49203 https://www.cve.org/CVERecord?id=CVE-2024-49203 Référence CVE CVE-2024-5171 https://www.cve.org/CVERecord?id=CVE-2024-5171 Référence CVE CVE-2024-51741 https://www.cve.org/CVERecord?id=CVE-2024-51741 Référence CVE CVE-2024-51744 https://www.cve.org/CVERecord?id=CVE-2024-51744 Référence CVE CVE-2024-52522 https://www.cve.org/CVERecord?id=CVE-2024-52522 Référence CVE CVE-2024-52616 https://www.cve.org/CVERecord?id=CVE-2024-52616 Référence CVE CVE-2024-53427 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-027752Redis Ltd. の Redis 等複数ベンダの製品における解放済みメモリの使用に関する脆弱性

Redis Ltd. の Redis 等複数ベンダの製品には、解放済みメモリの使用に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
redis: >= 7.4.0, < 7.4.2, >= 7.2.0, < 7.2.7, < 6.2.17
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 6 Jan 2025 · Last source change 19 Mar 2025, 20:14 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-42220
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2024-42220↗CVE authority or vendor reference · GitHub GHSA-39H2-X6C4-6W4C↗Public exploit reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-46981 · cve.blacktree.nl