# CVE-2021-32672: Vulnerability in Lua Debugger in Redis


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Oct 2021
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2021-32672, AZL-6847, BIT-keydb-2021-32672, BIT-redis-2021-32672, BIT-valkey-2021-32672, CLEANSTART-2026-AE22523, DEBIAN-CVE-2021-32672, GHSA-9mj9-xx53-qmxm, OESA-2021-1394, OESA-2022-1866, UBUNTU-CVE-2021-32672

## What is CVE-2021-32672?

CVE-2021-32672 is a medium-severity vulnerability in Debian Debian Linux, published on 4 Oct 2021. 

### Official description

Redis is an open source, in-memory database that persists on disk. When using the Redis Lua Debugger, users can send malformed requests that cause the debugger’s protocol parser to read data beyond the actual buffer. This issue affects all versions of Redis with Lua debugging support (3.2 or newer). The problem is fixed in versions 6.2.6, 6.0.16 and 5.0.14.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2021-32672?

3 open source packages ship an affected version, including keydb, redis and valkey. It affects 8 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keydb` | Bitnami | From 3.2.0 | 5.0.14, 6.0.16, 6.2.6 |
| `redis` | Bitnami | From 3.2.0 | 5.0.14, 6.0.16, 6.2.6 |
| `valkey` | Bitnami | From 3.2.0 | 5.0.14, 6.0.16, 6.2.6 |

Products: Debian Debian Linux, Fedoraproject Fedora, Netapp Management Services for Element Software, Netapp Management Services for Netapp Hci, Oracle Communications Operations Monitor, Redhat Enterprise Linux, Redhat Software Collections, Redis Redis.

## How do I fix CVE-2021-32672?

Upgrade keydb to a fixed version for your release line: 5.0.14, 6.0.16 or 6.2.6.

## Is CVE-2021-32672 being exploited?

There is no known exploitation of CVE-2021-32672 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32672 and fix it if it is affected.

What it is: CVE-2021-32672 is a medium-severity vulnerability in Debian Debian Linux, published on 4 Oct 2021. 
Exploitation: There is no known exploitation of CVE-2021-32672 in the wild and no public exploit code.

Affected packages and fixed versions:
- keydb (Bitnami): affected from 3.2.0; fixed in 5.0.14, 6.0.16, 6.2.6
- redis (Bitnami): affected from 3.2.0; fixed in 5.0.14, 6.0.16, 6.2.6
- valkey (Bitnami): affected from 3.2.0; fixed in 5.0.14, 6.0.16, 6.2.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-32672/ (Markdown: https://insights.sbomify.com/CVE-2021-32672/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-32672
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-32672
- OSV: https://osv.dev/vulnerability/CVE-2021-32672

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-32672/
Summaries are generated and may contain mistakes; the official description above is the record.