A buffer over-read issue was discovered in Suricata 4.1.x before 4.1.4. If the input of the decode-mpls.c function DecodeMPLS is composed only of a packet of source address and destination address plus the correct type field and the right number for shim, an attacker can manipulate the control flow, such that the condition to leave the loop is true. After leaving the loop, the network packet has a length of 2 bytes. There is no validation of this length. Later on, the code tries to read at an empty position, leading to a crash.
References
| Link | Resource |
|---|---|
| https://lists.openinfosecfoundation.org/pipermail/oisf-announce/ | Third Party Advisory |
| https://suricata-ids.org/2019/04/30/suricata-4-1-4-released/ | Patch Vendor Advisory |
| https://lists.openinfosecfoundation.org/pipermail/oisf-announce/ | Third Party Advisory |
| https://suricata-ids.org/2019/04/30/suricata-4-1-4-released/ | Patch Vendor Advisory |
Configurations
History
21 Nov 2024, 04:18
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://lists.openinfosecfoundation.org/pipermail/oisf-announce/ - Third Party Advisory | |
| References | () https://suricata-ids.org/2019/04/30/suricata-4-1-4-released/ - Patch, Vendor Advisory |
Information
Published : 2019-05-13 17:29
Updated : 2024-11-21 04:18
NVD link : CVE-2019-10050
Mitre link : CVE-2019-10050
CVE.ORG link : CVE-2019-10050
JSON object : View
Products Affected
oisf
- suricata
CWE
CWE-125
Out-of-bounds Read