pysec-2023-45
Vulnerability from pysec
Published
2023-03-26 19:15
Modified
2023-06-05 01:13
Details
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.
Impacted products
Name | purl |
---|---|
redis | pkg:pypi/redis |
Aliases
{ affected: [ { package: { ecosystem: "PyPI", name: "redis", purl: "pkg:pypi/redis", }, ranges: [ { events: [ { introduced: "4.2.0", }, { fixed: "4.3.6", }, { introduced: "4.4.0", }, { fixed: "4.4.3", }, { introduced: "4.5.0", }, { fixed: "4.5.3", }, ], type: "ECOSYSTEM", }, ], versions: [ "4.2.0", "4.2.1", "4.2.2", "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", ], }, ], aliases: [ "CVE-2023-28858", ], details: "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.", id: "PYSEC-2023-45", modified: "2023-06-05T01:13:00.293462Z", published: "2023-03-26T19:15:00Z", references: [ { type: "WEB", url: "https://github.com/redis/redis-py/compare/v4.3.5...v4.3.6", }, { type: "WEB", url: "https://github.com/redis/redis-py/pull/2641", }, { type: "ARTICLE", url: "https://openai.com/blog/march-20-chatgpt-outage", }, { type: "REPORT", url: "https://github.com/redis/redis-py/issues/2624", }, { type: "WEB", url: "https://github.com/redis/redis-py/compare/v4.4.2...v4.4.3", }, { type: "WEB", url: "https://github.com/redis/redis-py/compare/v4.5.2...v4.5.3", }, ], }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.