Executive Summary

Informations
Name CVE-2025-21605 First vendor Publication 2025-04-23
Vendor Cve Last vendor Modification 2025-06-02

Security-Database Scoring CVSS v3

Cvss vector : N/A
Overall CVSS Score NA
Base Score NA Environmental Score NA
impact SubScore NA Temporal Score NA
Exploitabality Sub Score NA
 
Calculate full CVSS 3.0 Vectors scores

Security-Database Scoring CVSS v2

Cvss vector :
Cvss Base Score N/A Attack Range N/A
Cvss Impact Score N/A Attack Complexity N/A
Cvss Expoit Score N/A Authentication N/A
Calculate full CVSS 2.0 Vectors scores

Detail

Redis is an open source, in-memory database that persists on disk. In versions starting at 2.6 and prior to 7.4.3, An unauthenticated client can cause unlimited growth of output buffers, until the server runs out of memory or is killed. By default, the Redis configuration does not limit the output buffer of normal clients (see client-output-buffer-limit). Therefore, the output buffer can grow unlimitedly over time. As a result, the service is exhausted and the memory is unavailable. When password authentication is enabled on the Redis server, but no password is provided, the client can still cause the output buffer to grow from "NOAUTH" responses until the system will run out of memory. This issue has been patched in version 7.4.3. An additional workaround to mitigate this problem without patching the redis-server executable is to block access to prevent unauthenticated users from connecting to Redis. This can be done in different ways. Either using network access control tools like firewalls, iptables, security groups, etc, or enabling TLS and requiring users to authenticate using client side certificates.

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21605

Sources (Detail)

https://github.com/redis/redis/releases/tag/7.4.3
https://github.com/redis/redis/security/advisories/GHSA-r67f-p999-2gff
https://github.com/valkey-io/valkey/releases/tag/8.1.1
https://lists.debian.org/debian-lts-announce/2025/05/msg00014.html
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
Date Informations
2025-06-02 09:20:03
  • Multiple Updates
2025-05-27 02:52:08
  • First insertion