CVE-2022-33105
First published: Wed Jun 22 2022(Updated: )
Redis v7.0 was discovered to contain a memory leak via the component streamGetEdgeID.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Redis Redis | =7.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/redis/redis/commit/4a7a4e42db8ff757cdf3f4a824f66426036034ef
- https://github.com/redis/redis/pull/10753
- https://github.com/redis/redis/pull/10829
- https://raw.githubusercontent.com/redis/redis/7.0.1/00-RELEASENOTES
- https://security.gentoo.org/glsa/202209-17
- https://security.netapp.com/advisory/ntap-20220729-0005/
Frequently Asked Questions
What is CVE-2022-33105?
CVE-2022-33105 refers to a vulnerability discovered in Redis v7.0 that allows for a memory leak via the component streamGetEdgeID.
What is the severity of CVE-2022-33105?
The severity of CVE-2022-33105 is high, with a severity score of 7.5.
How does CVE-2022-33105 affect Redis v7.0?
CVE-2022-33105 affects Redis v7.0 by causing a memory leak through the component streamGetEdgeID.
How can I fix CVE-2022-33105?
To fix CVE-2022-33105, it is recommended to update to a patched version of Redis v7.0.
Are there any references related to CVE-2022-33105?
Yes, you can find more information about CVE-2022-33105 in the following references: - [Github Commit](https://github.com/redis/redis/commit/4a7a4e42db8ff757cdf3f4a824f66426036034ef) - [Github Pull Request](https://github.com/redis/redis/pull/10753) - [Github Pull Request](https://github.com/redis/redis/pull/10829)
- collector/nvd-index
- agent/references
- agent/tags
- agent/type
- agent/weakness
- agent/severity
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- agent/softwarecombine
- agent/remedy
- collector/mitre-cve
- source/MITRE
- vendor/redis
- canonical/redis redis
- version/redis redis/7.0