dbcve.org
RedisDatabase / datastore · Redislabs

CVE-2015-4335

HIGH · 10.0 CVSS v2.0 Published 2015-06-09
Fix available
A fix is available. Upgrade to after 2.8.20 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
Redis before 2.8.21 and 3.x before 3.0.2 allows remote attackers to execute arbitrary Lua bytecode via the eval command.

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

Redis versions before 2.8.21 and 3.x before 3.0.2 contain a vulnerability in the Lua script execution functionality. The eval command improperly validates or restricts Lua bytecode, allowing remote authenticated attackers to execute arbitrary Lua code on the server, leading to potential remote code execution.

MitigationUpgrade Redis to version 2.8.21 or later (or 3.0.2 or later for 3.x branches). As an interim control, restrict network access to Redis instances and disable the eval command via configuration if immediate patching is not feasible.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RedisDatabase / datastore
Affected:<= 2.8.20= 3.0.0= 3.0.1
Debian LinuxOperating system
Affected:= 8.0= 9.0

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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Check installed Redis version
    Run 'redis-cli INFO' and look for 'redis_version:' field, or run 'redis-server --version' / 'dpkg -l | grep redis' on Debian
    Affected if Version is below 2.8.21, or is exactly 3.0.0 or 3.0.1
  2. Confirm eval command is available
    Run 'redis-cli COMMAND INFO eval' and verify the command exists (not returned as null)
    Affected if The eval command is present and not renamed or disabled in the configuration
  3. Check if Lua scripting is enabled
    Run 'redis-cli CONFIG GET enable-commands' or inspect redis.conf for 'enable-commands' directive, or test with 'redis-cli EVAL "return 1" 0'
    Affected if Lua script execution (eval, evalsha, script commands) is enabled in the configuration
  4. Verify network exposure
    Run 'redis-cli CONFIG GET bind' or check redis.conf for 'bind' directive, or use 'netstat -tlnp | grep 6379'
    Affected if Redis is bound to 0.0.0.0 or an accessible IP address, allowing remote connections

You are affected if your Redis version is below 2.8.21 (or 3.0.0/3.0.1) AND the eval command is enabled AND the instance is network-accessible to untrusted users.

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
Upgrade available Upgrade to a release after 2.8.20
Vendor patch github.com →
Interim mitigation

Upgrade Redis to version 2.8.21 or later (or 3.0.2 or later for 3.x branches). As an interim control, restrict network access to Redis instances and disable the eval command via configuration if immediate patching is not feasible.

Recommended fix High confidence

Redis 2.8.21 (for 2.8.x line) or Redis 3.0.2+ (for 3.0.x line)

  1. 1. Check current Redis version using: redis-server --version or redis-cli INFO
  2. 2. Backup Redis data and configuration: cp /etc/redis/redis.conf /etc/redis/redis.conf.backup and (if using persistence) backup RDB/AOF files
  3. 3. For Redis 2.8.x: Upgrade to Redis 2.8.21 or later
  4. 4. For Redis 3.0.x: Upgrade to Redis 3.0.2 or later
  5. 5. For Debian systems: Run apt-get update && apt-get install redis-server
  6. 6. Verify the new version is running: redis-server --version and redis-cli INFO
  7. 7. Test that the eval command works correctly with the patched version
Caveat Minor version upgrades typically maintain backwards compatibility; however, test Lua scripts after upgrade as some edge case behaviors may differ

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

Fix this in Redis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4335 — 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-2015-4335 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