Crash-report truncation via invalid pointer backtrace
Published Oct 21, 2022 · Updated Apr 15, 2025
Crash-reporting failure in Redis 6.2.0 through 6.2.7 and 7.0.0 through 7.0.5 allows local users to truncate crash diagnostics. In sigsegvHandler in src/debug.c, backtrace dereferences the invalid instruction pointer that caused the original crash, triggering a second crash before the full report is logged. The path is reachable only after Redis has already crashed, and Redis disputes any additional service interruption beyond loss of diagnostic output.
Summary
What happened
Crash-reporting failure in Redis 6.2.0 through 6.2.7 and 7.0.0 through 7.0.5 allows local users to truncate crash diagnostics. In sigsegvHandler in src/debug.c, backtrace dereferences the invalid instruction pointer that caused the original crash, triggering a second crash before the full report is logged. The path is reachable only after Redis has already crashed, and Redis disputes any additional service interruption beyond loss of diagnostic output.
The record
- CVE
- CVE-2022-3647
- Published
- Oct 21, 2022
- Updated
- Apr 15, 2025
- Vendor
- Redis
- Product
- Redis
- Classifications
- CWE-404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=6.2.0
- Affected versionversion=6.2.1
- Affected versionversion=6.2.2
- Affected versionversion=6.2.3
- Affected versionversion=6.2.4
- Affected versionversion=6.2.5
- Affected versionversion=6.2.6
- Affected versionversion=6.2.7
- Affected versionversion=7.0.0
- Affected versionversion=7.0.1
- Affected versionversion=7.0.2
- Affected versionversion=7.0.3
- Affected versionversion=7.0.4
- Affected versionversion=7.0.5
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