Google Cloud Iot Device Sdk Embedded C
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Google Cloud Iot Device Sdk Embedded C.
By the Year
In 2025 there have been 0 vulnerabilities in Google Cloud Iot Device Sdk Embedded C. Cloud Iot Device Sdk Embedded C did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 0 | 0.00 |
| 2021 | 1 | 7.80 |
| 2020 | 0 | 0.00 |
| 2019 | 0 | 0.00 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Cloud Iot Device Sdk Embedded C vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Google Cloud Iot Device Sdk Embedded C Security Vulnerabilities
In IoT Devices SDK, there is an implementation of calloc() that doesn't have a length check
CVE-2021-22547
7.8 - High
- May 04, 2021
In IoT Devices SDK, there is an implementation of calloc() that doesn't have a length check. An attacker could pass in memory objects larger than the buffer and wrap around to have a smaller buffer than required, allowing the attacker access to the other parts of the heap. We recommend upgrading the Google Cloud IoT Device SDK for Embedded C used to 1.0.3 or greater.
Classic Buffer Overflow
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Google Cloud Iot Device Sdk Embedded C or by Google? Click the Watch button to subscribe.
