CVE-2019-15134
First published: Sat Aug 17 2019(Updated: )
RIOT through 2019.07 contains a memory leak in the TCP implementation (gnrc_tcp), allowing an attacker to consume all memory available for network packets and thus effectively stopping all network threads from working. This is related to _receive in sys/net/gnrc/transport_layer/tcp/gnrc_tcp_eventloop.c upon receiving an ACK before a SYN.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Riot-os Riot | <=2019.07 |
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
Frequently Asked Questions
What is the severity of CVE-2019-15134?
CVE-2019-15134 has a moderate severity due to its potential to cause network service disruptions.
How do I fix CVE-2019-15134?
To fix CVE-2019-15134, upgrade to a version of RIOT later than 2019.07 that has the memory leak issue patched.
What components are affected by CVE-2019-15134?
CVE-2019-15134 affects the TCP implementation found in the GNRC networking stack of RIOT OS.
How can CVE-2019-15134 be exploited?
An attacker can exploit CVE-2019-15134 by sending a flood of TCP packets to consume all available memory allocated for network operations.
Is there a workaround for CVE-2019-15134?
Currently, there is no specific workaround for CVE-2019-15134 other than applying the recommended update to mitigate the issue.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- agent/author
- agent/remedy
- agent/severity
- agent/weakness
- agent/tags
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- vendor/riot-os
- canonical/riot-os riot
- version/riot-os riot/2019.07