CVE-2020-16843
Summary
| CVE | CVE-2020-16843 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2020-08-04 20:15:00 UTC |
| Updated | 2020-08-19 18:39:00 UTC |
| Description | In Firecracker 0.20.x before 0.20.1 and 0.21.x before 0.21.2, the network stack can freeze under heavy ingress traffic. This can result in a denial of service on the microVM when it is configured with a single network interface, and an availability problem for the microVM network interface on which the issue is triggered. |
Risk And Classification
Problem Types: NVD-CWE-noinfo
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Amazon | Firecracker | 0.20.0 | All | All | All |
| Application | Amazon | Firecracker | 0.21.0 | All | All | All |
| Application | Amazon | Firecracker | 0.21.1 | All | All | All |
| Application | Amazon | Firecracker | 0.20.0 | All | All | All |
| Application | Amazon | Firecracker | 0.21.0 | All | All | All |
| Application | Amazon | Firecracker | 0.21.1 | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| CVE-2020-16843: Firecracker v0.20.0, v0.21.0 and v0.21.1 network stack can freeze under heavy ingress traffic · Issue #2057 · firecracker-microvm/firecracker · GitHub | MISC | github.com | Mitigation, Third Party Advisory |
| oss-security - CVE-2020-16843: Firecracker v0.20.0, v0.21.0 and v0.21.1 network stack can freeze under heavy ingress traffic | MISC | www.openwall.com | Mailing List, Third Party Advisory |
| oss-security - CVE-2020-16843: Firecracker v0.20.0, v0.21.0 and v0.21.1 network stack can freeze under heavy ingress traffic | MLIST | www.openwall.com | Mailing List, Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.