Impact
An out-of-bounds read can be caused by an incoming DIO message when using the RPL-Lite implementation in the Contiki-NG operating system.
More specifically, the prefix information of the DIO message contains a field that specifies the length of an IPv6 address prefix. The value of this field is not validated, which means that an attacker can set a value that is longer than the maximum prefix length. Subsequently, a memcmp function call that compares different prefixes can be called with a length argument that surpasses the boundary of the array allocated for the prefix, causing an out-of-bounds read.
Patches
The problem has been patched in the "develop" branch of Contiki-NG, and is expected to be included in the next release.
Workarounds
One can apply the changes in Contiki-NG pull request #2721 to patch the system.
For more information
If you have any questions or comments about this advisory:
Open an issue in https://github.com/contiki-ng/contiki-ng
Email us at security@contiki-ng.org
sploitem Reporter
Impact
An out-of-bounds read can be caused by an incoming DIO message when using the RPL-Lite implementation in the Contiki-NG operating system.
More specifically, the prefix information of the DIO message contains a field that specifies the length of an IPv6 address prefix. The value of this field is not validated, which means that an attacker can set a value that is longer than the maximum prefix length. Subsequently, a memcmp function call that compares different prefixes can be called with a length argument that surpasses the boundary of the array allocated for the prefix, causing an out-of-bounds read.
Patches
The problem has been patched in the "develop" branch of Contiki-NG, and is expected to be included in the next release.
Workarounds
One can apply the changes in Contiki-NG pull request #2721 to patch the system.
For more information
If you have any questions or comments about this advisory:
Open an issue in https://github.com/contiki-ng/contiki-ng
Email us at security@contiki-ng.org