Buffer overflow in Google Cloud Iot Device Sdk For Embedded C
CVE-2021-22547
- CVSS v3
- 6.3 Medium
- Public exploits
- None known
- EPSS
- 0.002 · 12.2th percentile
- Published
- 2021-05-04
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.
Vulnerability class: Buffer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.3 (Medium). Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N.
- Attack Vector
- Local
AV:L - Attack Complexity
- High
AC:H - Privileges Required
- Low
PR:L - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- High
C:H - Integrity
- High
I:H - Availability
- None
A:N
EPSS exploit prediction
EPSS 0.002, 12.2th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Google Cloud Iot Device Sdk For Embedded C
- Google Llc Cloud Iot Device Sdk For Embedded C — versions unspecified
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (jornverhoeven/adrian). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/GoogleCloudPlatform/iot-device-sdk-embedded-c/blob/master/RELEASE-NO… (Third Party Advisory, Release Notes)
- github.com/GoogleCloudPlatform/iot-device-sdk-embedded-c/pull/119 (Patch, Third Party Advisory)