dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2024-51480

HIGH · 7.0 CVSS v3.1 Published 2025-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
RedisTimeSeries is a time-series database (TSDB) module for Redis, by Redis. Executing one of these commands TS.QUERYINDEX, TS.MGET, TS.MRAGE, TS.MREVRANGE by an authenticated user, using specially crafted command arguments may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. This vulnerability is fixed in 1.6.20, 1.8.15, 1.10.15, and 1.12.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

RedisTimeSeries module for Redis contains an integer overflow vulnerability in the command handlers for TS.QUERYINDEX, TS.MGET, TS.MRAGE, and TS.MREVRANGE. When an authenticated user provides specially crafted command arguments, the integer overflow leads to a heap overflow that can potentially be exploited for remote code execution.

MitigationUpgrade RedisTimeSeries to versions 1.6.20, 1.8.15, 1.10.15, or 1.12.3 or later. If immediate upgrade is not possible, restrict authenticated access to the Redis instance and monitor for suspicious command patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm RedisTimeSeries module is loaded
    Run the Redis command MODULE LIST and check if the output contains a module with name containing 'timeseries' or 'redistimeseries'
    Affected if The module is not loaded means the vulnerability does not apply
  2. Identify the installed RedisTimeSeries version
    Run the Redis command MODULE LIST and look for the 'ver' (version) field associated with the RedisTimeSeries module
    Affected if The version is unknown or falls below 1.6.20, 1.8.15, 1.10.15, or 1.12.3 (check the relevant branch for your version)
  3. Compare your version against affected ranges
    If your version is 1.6.x, you are affected if below 1.6.20. If 1.8.x, affected if below 1.8.15. If 1.10.x, affected if below 1.10.15. If 1.12.x, affected if below 1.12.3
    Affected if Your installed version is below any of these threshold versions in its respective release branch
  4. Verify the vulnerable commands are accessible
    Run TS.QUERYINDEX (or TS.MGET, TS.MRANGE, TS.MREVRANGE) to confirm these commands are available in your Redis instance. Use INFO command to check if requirepass or ACLs are configured
    Affected if The commands execute without error AND the instance allows authenticated user access (the vulnerability requires an authenticated user to send specially crafted arguments)

You are affected if the RedisTimeSeries module is loaded, your version is below the fixed releases (1.6.20, 1.8.15, 1.10.15, or 1.12.3), and authenticated users can execute the TS.QUERYINDEX, TS.MGET, TS.MRANGE, or TS.MREVRANGE commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade RedisTimeSeries to versions 1.6.20, 1.8.15, 1.10.15, or 1.12.3 or later. If immediate upgrade is not possible, restrict authenticated access to the Redis instance and monitor for suspicious command patterns.

Recommended fix High confidence

1.12.3 (latest stable) or version appropriate to your current branch: 1.6.20, 1.8.15, 1.10.15

  1. 1. Identify current RedisTimeSeries version by running `MODULE LIST` or checking module info with `MODULE INFO mod_name timestate` in Redis CLI
  2. 2. If running version 1.6.x or earlier, upgrade to 1.6.20
  3. 3. If running version 1.7.x or 1.8.x, upgrade to 1.8.15
  4. 4. If running version 1.9.x or 1.10.x, upgrade to 1.10.15
  5. 5. If running version 1.11.x or 1.12.x, upgrade to 1.12.3
  6. 6. Reload the RedisTimeSeries module in Redis using `MODULE LOAD` command with the new .so file
  7. 7. Restart Redis service if module was loaded via config file, then verify fix with `MODULE INFO mod_name timestate`

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51480 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51480 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data