Service crash via unbounded Redis parser allocation
Published Aug 14, 2025 · Updated Nov 4, 2025
Uncontrolled resource consumption in Apache bRPC before 1.14.1 allows remote attackers to crash Redis-enabled services via crafted traffic. The Redis protocol parser allocates arrays and strings from network-supplied integer lengths; in 1.14.0, integer overflow bypasses its allocation limit. Exposure requires a bRPC Redis server to accept untrusted clients or a bRPC Redis client to consume replies from an untrusted service.
Summary
What happened
Uncontrolled resource consumption in Apache bRPC before 1.14.1 allows remote attackers to crash Redis-enabled services via crafted traffic. The Redis protocol parser allocates arrays and strings from network-supplied integer lengths; in 1.14.0, integer overflow bypasses its allocation limit. Exposure requires a bRPC Redis server to accept untrusted clients or a bRPC Redis client to consume replies from an untrusted service.
The record
- CVE
- CVE-2025-54472
- Published
- Aug 14, 2025
- Updated
- Nov 4, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache bRPC
- Classifications
- CWE-400, CWE-190, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 14, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.14.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo