Excessive memory allocation in s2n-quic
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| AWS | s2n-quic | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Aws | S2n-quic |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9q54-f358-3fqf | s2n-quic has excessive memory allocation |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.291% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Unbounded memory allocation in the CRYPTO frame reassembler in s2n-quic before 1.8.2 may allow an unauthenticated remote actor to cause a denial of service (degraded availability) by sending crafted QUIC Initial packets. To remediate this issue, users should upgrade to v1.8.2. | |
| Title | Excessive memory allocation in s2n-quic | |
| First Time appeared |
Aws
Aws s2n-quic |
|
| Weaknesses | CWE-770 | |
| CPEs | cpe:2.3:a:aws:s2n-quic:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aws
Aws s2n-quic |
|
| References |
| |
| Metrics |
cvssV3_1
|