CVE-2021-22684: Integer Overflow
First published: Tue Aug 31 2021(Updated: )
Tizen RT RTOS version 3.0.GBB is vulnerable to integer wrap-around in functions_calloc and mm_zalloc. This improper memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash
Credit: ics-cert@hq.dhs.gov
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Samsung Tizen RT | <=3.0 | |
| Amazon FreeRTOS | ||
| Apache NuttX | ||
| ARM CMSIS-RTOS2 | ||
| Arm Mbed OS | ||
| Arm Mbed ualloc | ||
| QNX | ||
| BlackBerry QNX OS for Safety | ||
| BlackBerry QNX OS for Medical | ||
| QNX | ||
| Mongoose OS | ||
| eCosCentric eCosPro RTOS | ||
| Google Cloud IoT Device SDK | ||
| MediaTek LinkIt SDK | ||
| Micrium OS | ||
| Micrium uC/OS | ||
| NXP MCUXpresso SDK | ||
| NXP MQX | ||
| newlib | ||
| RIOT OS | ||
| Samsung Tizen RT | ||
| TencentOS-tiny | ||
| Texas Instruments SimpleLink CC32XX | ||
| Texas Instruments SimpleLink MSP432E4 SDK | ||
| Texas Instruments SimpleLink CC13X2 SDK | ||
| Texas Instruments SimpleLink CC26XX | ||
| Texas Instruments SimpleLink CC32XX | ||
| uClibc | ||
| Wind River VxWorks | ||
| Zephyr Project RTOS |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2021-22684?
CVE-2021-22684 is classified as a medium severity vulnerability due to potential arbitrary memory allocation leading to unexpected behavior.
How do I fix CVE-2021-22684?
To fix CVE-2021-22684, update to the latest version of the affected software that addresses the integer wrap-around issue.
What can happen if CVE-2021-22684 is exploited?
If exploited, CVE-2021-22684 can lead to arbitrary memory allocation, which may cause application crashes or unstable behavior.
Which products are affected by CVE-2021-22684?
CVE-2021-22684 affects various products including Samsung TizenRT and versions of FreeRTOS, NuttX, and others, typically prior to specific versions.
Is there a workaround for CVE-2021-22684?
Currently, the best mitigation for CVE-2021-22684 is to upgrade the affected software to a version that has been patched to resolve the vulnerability.
- agent/type
- agent/author
- agent/severity
- agent/weakness
- agent/references
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/trending
- agent/source
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/ics-cert-advisory
- source/ICS
- agent/software-canonical-lookup
- vendor/samsung
- canonical/samsung tizen rt
- version/samsung tizen rt/3.0
- vendor/multiple
- canonical/amazon freertos
- canonical/apache nuttx
- canonical/arm cmsis-rtos2
- canonical/arm mbed os
- canonical/arm mbed ualloc
- canonical/qnx
- canonical/blackberry qnx os for safety
- canonical/blackberry qnx os for medical
- canonical/mongoose os
- canonical/ecoscentric ecospro rtos
- canonical/google cloud iot device sdk
- canonical/mediatek linkit sdk
- canonical/micrium os
- canonical/micrium uc/os
- canonical/nxp mcuxpresso sdk
- canonical/nxp mqx
- canonical/newlib
- canonical/riot os
- canonical/tencentos-tiny
- canonical/texas instruments simplelink cc32xx
- canonical/texas instruments simplelink msp432e4 sdk
- canonical/texas instruments simplelink cc13x2 sdk
- canonical/texas instruments simplelink cc26xx
- canonical/uclibc
- canonical/wind river vxworks
- canonical/zephyr project rtos