redis-py up to 4.3.5/4.4.2/4.5.2 Async Command information disclosure

Summaryinfo

A vulnerability was found in redis-py up to 4.3.5/4.4.2/4.5.2. It has been classified as problematic. The impacted element is an unknown function of the component Async Command Handler. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2023-28858. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in redis-py up to 4.3.5/4.4.2/4.5.2 and classified as problematic. This issue affects an unknown code block of the component Async Command Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

redis-py before 4.5.3, as used in ChatGPT and other products, leaves a connection open after canceling an async Redis command at an inopportune time (in the case of a pipeline operation), and can send response data to the client of an unrelated request in an off-by-one manner. The fixed versions for this CVE Record are 4.3.6, 4.4.3, and 4.5.3; however, CVE-2023-28859 is a separate vulnerability.

The weakness was presented 03/27/2023 as 2624. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-28858 since 03/26/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 4.3.6, 4.4.3 or 4.5.3 eliminates this vulnerability. Applying a patch 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 EUVD (EUVD-2023-0222). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• redis-py

Version

• 4.3.0
• 4.3.1
• 4.3.2
• 4.3.3
• 4.3.4
• 4.3.5
• 4.4.0
• 4.4.1
• 4.4.2
• 4.5.0
• 4.5.1
• 4.5.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion