← Back
UBUNTU-CVE-2024-51741
Vulnerability in redis (UBUNTU-CVE-2024-51741)
Summary
vulnerability in redis (UBUNTU-CVE-2024-51741). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5:7.0.15-1ubuntu0.24.04.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2024-51741** has been found in redis.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade redis to **5:7.0.15-1ubuntu0.24.04.1** or later.
If unsure, ask your IT team or search "redis UBUNTU-CVE-2024-51741" on the vendor's site.
UBUNTU-CVE-2024-51741 (redis) —
Attack vector: local / no user interaction
Patched: `5:7.0.15-1ubuntu0.24.04.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (unclassified) exists in redis.
📍 Affected scope
redis — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5:7.0.15-1ubuntu0.24.04.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'redis' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'redis' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `redis` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade redis to 5:7.0.15-1ubuntu0.24.04.1ステージング環境で 5:7.0.15-1ubuntu0.24.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:24.04:LTS
redis
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5:7.0.15-1ubuntu0.24.04.1"}]}]
Ubuntu:24.04:LTS
valkey
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.8+dfsg1-0ubuntu0.24.04.2"}]}]
Ubuntu:25.10
redict
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:26.04:LTS
redict
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-7321-1
- advisory https://ubuntu.com/security/notices/USN-7359-1
- report https://ubuntu.com/security/CVE-2024-51741
- report https://www.cve.org/CVERecord?id=CVE-2024-51741
- report https://github.com/redis/redis/security/advisories/GHSA-prpq-rh5h-46g9
- report https://github.com/redis/redis/commit/15e212bf69de28d2b4585aa79cc2a40f49e4a94d
- report https://codeberg.org/redict/redict/issues/60
- report https://github.com/valkey-io/valkey/commit/7977c55ac9bea7d1443c32ef5ec020767c086d3a