An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. When the Urgent flag is set in a TCP packet, and the stack is configured to ignore the urgent data, the stack attempts to use the value of the Urgent pointer bytes to separate the Urgent data from the normal data, by calculating the offset at which the normal data should be present in the global buffer. However, the length of this offset is not checked; therefore, for large values of the Urgent pointer bytes, the data pointer can point to memory that is way beyond the data buffer in uip_process in uip.c.
References
Link | Resource |
---|---|
https://cert-portal.siemens.com/productcert/pdf/ssa-541018.pdf | Patch Third Party Advisory |
https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 | Third Party Advisory US Government Resource |
https://www.kb.cert.org/vuls/id/815128 | Third Party Advisory US Government Resource |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2020-12-11T22:24:38
Updated: 2021-03-09T14:06:21
Reserved: 2020-08-07T00:00:00
Link: CVE-2020-17437
JSON object: View
NVD Information
Status : Analyzed
Published: 2020-12-11T23:15:12.683
Modified: 2022-08-08T14:57:57.177
Link: CVE-2020-17437
JSON object: View
Redhat Information
No data.
CWE