Summary
FreeRTOS-Plus-TCP is an open source TCP/IP stack implementation specifically designed for FreeRTOS. The stack provides a standard Berkeley sockets interface and supports essential networking protocols including IPv6, ARP, DHCP, DNS, LLMNR, mDNS, NBNS, RA, ND, ICMP, and ICMPv6. An issue exists where, under certain circumstances, FreeRTOS-Plus-TCP may allow Buffer Over-read.
Impact
A Buffer Over-read when processing a IPv6 packet with incorrect payload lengths in the packet header.
This issue only affects applications using IPv6.
Impacted versions: v4.0.0 to v4.3.3, if IPv6 support is enabled.
Patches
This issue has been addressed in FreeRTOS-Plus-TCP version 4.3.4. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds
None.
References
If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to [email protected]. Please do not create a public GitHub issue.
Acknowledgement
We would like to thank Ivan Gotovchits of Mayhem Security for collaborating on this issue through the coordinated vulnerability disclosure process.
Summary
FreeRTOS-Plus-TCP is an open source TCP/IP stack implementation specifically designed for FreeRTOS. The stack provides a standard Berkeley sockets interface and supports essential networking protocols including IPv6, ARP, DHCP, DNS, LLMNR, mDNS, NBNS, RA, ND, ICMP, and ICMPv6. An issue exists where, under certain circumstances, FreeRTOS-Plus-TCP may allow Buffer Over-read.
Impact
A Buffer Over-read when processing a IPv6 packet with incorrect payload lengths in the packet header.
This issue only affects applications using IPv6.
Impacted versions: v4.0.0 to v4.3.3, if IPv6 support is enabled.
Patches
This issue has been addressed in FreeRTOS-Plus-TCP version 4.3.4. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds
None.
References
If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to [email protected]. Please do not create a public GitHub issue.
Acknowledgement
We would like to thank Ivan Gotovchits of Mayhem Security for collaborating on this issue through the coordinated vulnerability disclosure process.