CVE-2025-54472 Apache bRPC: Redis Parser Remote Denial of Service
Attackers can crash Apache bRPC services by sending malicious Redis protocol packets that trigger excessive memory allocation.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-54472?
CVE-2025-54472 is a high-severity denial of service vulnerability in Apache bRPC, published on 14 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Unlimited memory allocation in redis protocol parser in Apache bRPC (all versions < 1.14.1) on all platforms allows attackers to crash the service via network.
Root Cause: In the bRPC Redis protocol parser code, memory for arrays or strings of corresponding sizes is allocated based on the integers read from the network. If the integer read from the network is too large, it may cause a bad alloc error and lead to the program crashing. Attackers can exploit this feature by sending special data packets to the bRPC service to carry out a denial-of-service attack on it. The bRPC 1.14.0 version tried to fix this issue by limited the memory allocation size, however, the limitation checking code is not well implemented that may cause integer overflow and evade such limitation. So the 1.14.0 version is also vulnerable, although the integer range that affect version 1.14.0 is different from that affect version < 1.14.0.
Affected scenarios: Using bRPC as a Redis server to provide network services to untrusted clients, or using bRPC as a Redis client to call untrusted Redis services.
How to Fix: we provide two methods, you can choose one of them:
1. Upgrade bRPC to version 1.14.1. 2. Apply this patch ( https://github.com/apache/brpc/pull/3050 ) manually.
No matter you choose which method, you should note that the patch limits the maximum length of memory allocated for each time in the bRPC Redis parser. The default limit is 64M. If some of you redis request or response have a size larger than 64M, you might encounter error after upgrade. For such case, you can modify the gflag redis_max_allocation_size to set a larger limit.
Which versions are affected by CVE-2025-54472?
It affects 1 product.
Products include Apache Brpc.
How do I fix CVE-2025-54472?
No fix has been published for CVE-2025-54472 yet. Limit exposure of the affected software until one is available.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2025-54472 being exploited?
There is no known exploitation of CVE-2025-54472 in the wild and no public exploit code.
Other vulnerabilities in Apache bRPC
- CVE-2025-60021 Apache bRPC: Remote command injection vulnerability in heap builtin service
- CVE-2023-31039 Apache bRPC: ServerOptions.pid_file may cause arbitrary code execution
- CVE-2025-59789 Apache bRPC: Stack Exhaustion via Unbounded Recursion in JSON Parser
- CVE-2024-23452 Apache bRPC: HTTP request smuggling vulnerability
- CVE-2023-45757 Apache bRPC: The builtin service rpcz page has an XSS attack vulnerability
Sources
Also known as GHSA-fgf7-x5pv-vcc3.