CVE-2022-3647
Last modified
CVE-2022-3647 is a low-severity vulnerability rated 3.3/10 on the CVSS scale. ** DISPUTED ** A vulnerability, which was classified as problematic, was found in Redis up to 6.2.7/7.0.5. Affected is the function sigsegvHandler of the file debug.c of the component Crash Report. EPSS estimates a 0.57% chance of exploitation in the next 30 days.
Description
** DISPUTED ** A vulnerability, which was classified as problematic, was found in Redis up to 6.2.7/7.0.5. Affected is the function sigsegvHandler of the file debug.c of the component Crash Report. The manipulation leads to denial of service. The complexity of an attack is rather high. The exploitability is told to be difficult. The real existence of this vulnerability is still doubted at the moment. Upgrading to version 6.2.8 and 7.0.6 is able to address this issue. The patch is identified as 0bf90d944313919eb8e63d3588bf63a367f020a3. It is recommended to apply a patch to fix this issue. VDB-211962 is the identifier assigned to this vulnerability. NOTE: The vendor claims that this is not a DoS because it applies to the crash logging mechanism which is triggered after a crash has occurred.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Redis | Redis | < 6.2.8 |
| Redis | Redis | >= 7.0.0, < 7.0.6 |
References
- https://github.com/redis/redis/commit/0bf90d944313919eb8e63d3588bf63a367f020a3Exploit, Patch, Third Party Advisory
- https://vuldb.com/?ctiid.211962Permissions Required, Third Party Advisory, VDB Entry
- https://vuldb.com/?id.211962Third Party Advisory, VDB Entry
- https://github.com/redis/redis/commit/0bf90d944313919eb8e63d3588bf63a367f020a3Exploit, Patch, Third Party Advisory
- https://vuldb.com/?ctiid.211962Permissions Required, Third Party Advisory, VDB Entry
- https://vuldb.com/?id.211962Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-3647?
How severe is CVE-2022-3647?
How do I fix CVE-2022-3647?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-36464TOTOLINK A3700R V9.1.2u.6134_B20201202 was discovered to con…7.8
- CVE-2022-36465TOTOLINK A3700R V9.1.2u.6134_B20201202 was discovered to con…7.8
- CVE-2022-36466TOTOLINK A3700R V9.1.2u.6134_B20201202 was discovered to con…7.8
- CVE-2022-36467H3C B5 Mini B5MiniV100R005 was discovered to contain a stack…7.8
- CVE-2022-36468H3C B5 Mini B5MiniV100R005 was discovered to contain a stack…7.8
- CVE-2022-36469H3C B5 Mini B5MiniV100R005 was discovered to contain a stack…7.8
- CVE-2022-36470H3C B5 Mini B5MiniV100R005 was discovered to contain a stack…7.8
- CVE-2022-36471H3C B5 Mini B5MiniV100R005 was discovered to contain a stack…7.8
- CVE-2022-36472H3C B5 Mini B5MiniV100R005 was discovered to contain a stack…7.8
- CVE-2022-36473H3C B5 Mini B5MiniV100R005 was discovered to contain a stack…7.8
- CVE-2022-36474H3C B5 Mini B5MiniV100R005 was discovered to contain a stack…7.8
- CVE-2022-36475H3C B5 Mini B5MiniV100R005 was discovered to contain a stack…7.8
Are you affected by CVE-2022-3647?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
