Redis Crash Report debug.c sigsegvHandler denial of service ⚔ [Disputed]
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability, which was classified as problematic, was found in Redis (version unknown). Affected is the function
sigsegvHandler of the file debug.c of the component Crash Report. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The program does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. CVE summarizes:
A vulnerability, which was classified as problematic, was found in Redis. Affected is the function sigsegvHandler of the file debug.c of the component Crash Report. The manipulation leads to denial of service. The real existence of this vulnerability is still doubted at the moment. The name of the patch is 0bf90d944313919eb8e63d3588bf63a367f020a3. It is recommended to apply a patch to fix this issue. VDB-211962 is the identifier assigned to this vulnerability.
The weakness was disclosed 10/21/2022 as 0bf90d944313919eb8e63d3588bf63a367f020a3. The advisory is available at github.com. This vulnerability is traded as CVE-2022-3647. Technical details are known, but there is no available exploit.
The real existence of this vulnerability is still doubted at the moment. 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.
Applying the patch 0bf90d944313919eb8e63d3588bf63a367f020a3 is able to eliminate this problem. The bugfix is ready for download at github.com.
CVSSv3VulDB Meta Base Score: 4.6
VulDB Meta Temp Score: 4.5
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CNA Base Score: 3.1
CNA Vector (VulDB): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Denial of service
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Timeline10/21/2022 Advisory disclosed
10/21/2022 +0 days CVE reserved
10/21/2022 +0 days VulDB entry created
11/19/2022 +29 days VulDB last update
CVE: CVE-2022-3647 (🔒)
EntryCreated: 10/21/2022 07:59 PM
Updated: 11/19/2022 10:02 AM
Changes: 10/21/2022 07:59 PM (41), 11/19/2022 07:16 AM (1), 11/19/2022 07:18 AM (2), 11/19/2022 09:54 AM (2), 11/19/2022 10:02 AM (21)
Might our Artificial Intelligence support you?
Check our Alexa App!
No comments yet. Languages: en.
Please log in to comment.