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://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 |
| https://cert-portal.siemens.com/productcert/pdf/ssa-541018.pdf |
Configurations
Configuration 1 (hide)
| AND |
|
Information
Published : 2020-12-11 23:15
Updated : 2021-03-09 15:15
NVD link : CVE-2020-17437
Mitre link : CVE-2020-17437
JSON object : View
Products Affected
uip_project
- uip
contiki-os
- contiki
CWE
CWE-787
Out-of-bounds Write
