Search for packages
| purl | pkg:rpm/redhat/etcd@3.3.23-16?arch=el8ost |
| Next non-vulnerable version | None. |
| Latest non-vulnerable version | None. |
| Risk | 4.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-23k2-d1ex-abcn
Aliases: CVE-2024-4436 |
etcd: Incomplete fix for CVE-2022-41723 in OpenStack Platform | There are no reported fixed by versions. |
|
VCID-4c51-73a9-17f9
Aliases: CVE-2023-39322 |
Multiple vulnerabilities have been discovered in Go, the worst of which could lead to remote code execution. | There are no reported fixed by versions. |
|
VCID-5eck-adts-e3de
Aliases: CVE-2023-39326 |
Multiple vulnerabilities have been discovered in Go, the worst of which could lead to information leakage or a denial of service. | There are no reported fixed by versions. |
|
VCID-5tae-75u6-pugf
Aliases: CVE-2024-4438 |
etcd: Incomplete fix for CVE-2023-39325/CVE-2023-44487 in OpenStack Platform | There are no reported fixed by versions. |
|
VCID-6nrn-u58x-mben
Aliases: CVE-2024-1394 GHSA-78hx-gp6g-7mj6 |
Memory leaks in code encrypting and verifying RSA payloads Using crafted public RSA keys which are not compliant with SP 800-56B can cause a small memory leak when encrypting and verifying payloads. An attacker can leverage this flaw to gradually erode available memory to the point where the host crashes for lack of resources. Upon restart the attacker would have to begin again, but nevertheless there is the potential to deny service. | There are no reported fixed by versions. |
|
VCID-95zc-mxqu-tyfp
Aliases: CVE-2023-39318 |
Multiple vulnerabilities have been discovered in Go, the worst of which could lead to remote code execution. | There are no reported fixed by versions. |
|
VCID-a25b-3vep-y3gm
Aliases: CVE-2023-39319 |
Multiple vulnerabilities have been discovered in Go, the worst of which could lead to remote code execution. | There are no reported fixed by versions. |
|
VCID-aj2b-56uj-gkar
Aliases: CVE-2023-45288 GHSA-4v7x-pqxf-cx7m |
net/http, x/net/http2: close connections when receiving too many headers An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection. | There are no reported fixed by versions. |
|
VCID-x4ux-7vyz-eug9
Aliases: CVE-2023-39321 |
Multiple vulnerabilities have been discovered in Go, the worst of which could lead to remote code execution. | There are no reported fixed by versions. |
|
VCID-ybh3-wzu9-dued
Aliases: CVE-2024-4437 |
etcd: Incomplete fix for CVE-2021-44716 in OpenStack Platform | There are no reported fixed by versions. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||