Redis up to 6.0.17/6.2.10/7.0.8 algorithmic complexity

Summaryinfo

A vulnerability has been found in Redis up to 6.0.17/6.2.10/7.0.8 and classified as problematic. This impacts an unknown function. Performing a manipulation results in algorithmic complexity. This vulnerability is cataloged as CVE-2022-36021. The attack must be initiated from a local position. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Redis up to 6.0.17/6.2.10/7.0.8. It has been classified as problematic. This affects an unknown part. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. CWE is classifying the issue as CWE-407. An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. This is going to have an impact on availability. The summary by CVE is:

Redis is an in-memory database that persists on disk. Authenticated users can use string matching commands (like `SCAN` or `KEYS`) with a specially crafted pattern to trigger a denial-of-service attack on Redis, causing it to hang and consume 100% CPU time. The problem is fixed in Redis versions 6.0.18, 6.2.11, 7.0.9.

The weakness was shared 03/01/2023 as GHSA-jr7j-rfj5-8xqv. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-36021 since 07/15/2022. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 214525 (AlmaLinux 8 : redis:6 (ALSA-2025:0595)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.0.18, 6.2.11 or 7.0.9 eliminates this vulnerability. Applying the patch dcbfcb916ca1a269b3feef86ee86835294758f84 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (214525). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Redis

Version

• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.0.10
• 6.0.11
• 6.0.12
• 6.0.13
• 6.0.14
• 6.0.15
• 6.0.16
• 6.0.17
• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7
• 6.2.8
• 6.2.9
• 6.2.10
• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.0.7
• 7.0.8

License

• open-source

Website

• Product: https://github.com/redis/redis/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion