Authenticated code execution via undisclosed buffer overflow
Published Nov 6, 2023 · Updated Apr 29, 2025
Buffer overflow in RedisGraph 2.0.0 through 2.12.8 allows remote authenticated users to execute arbitrary code over the Redis service. The public record identifies an out-of-bounds write in post-authentication code logic but does not disclose the affected function, buffer, or triggering input. Valid Redis credentials and network access are required; successful exploitation runs attacker-controlled code in the Redis server's security context.
Summary
What happened
Buffer overflow in RedisGraph 2.0.0 through 2.12.8 allows remote authenticated users to execute arbitrary code over the Redis service. The public record identifies an out-of-bounds write in post-authentication code logic but does not disclose the affected function, buffer, or triggering input. Valid Redis credentials and network access are required; successful exploitation runs attacker-controlled code in the Redis server's security context.
The record
- CVE
- CVE-2023-47004
- Published
- Nov 6, 2023
- Updated
- Apr 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, CWE-787, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 6, 2023CVE publishedPublication date reported by the CVE source.
- Apr 29, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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