CVE Vulnerability

CVE-2020-5235

There is a potentially exploitable out of memory condition In Nanopb before 0.4.1, 0.3.9.5, and 0.2.9.4. When nanopb is compiled with PB_ENABLE_MALLOC, the message to be decoded contains a repeated string, bytes or message field and realloc() runs out of memory when expanding the array nanopb can end up calling `free()` on a pointer value that comes from uninitialized memory. Depending on platform this can result in a crash or further memory corruption, which may be exploitable in some cases. This problem is fixed in nanopb-0.4.1, nanopb-0.3.9.5, nanopb-0.2.9.4.

7.5 /10

CVSS v2.0 :

V3 Legend

Vector :

Exploitability : 10 / Impact : 6.4

Attack Vector

Attack Complexity

Privileges Required

User Interaction

Confidentiality Impact PARTIAL

Integrity Impact PARTIAL

Availability Impact PARTIAL

Scope

9.8 /10

CVSS v3.0 : CRITICAL

V3 Legend

Vector :

Exploitability : 3.9 / Impact : 5.9

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://github.com/nanopb/nanopb/commit/45582f1f97f49e2abfdba1463d1e1027682d9856 Patch Third Party Advisory
https://github.com/nanopb/nanopb/commit/7b396821ddd06df8e39143f16e1dc0a4645b89a3 Patch Third Party Advisory
https://github.com/nanopb/nanopb/security/advisories/GHSA-gcx3-7m76-287p Patch Third Party Advisory
https://github.com/nanopb/nanopb/commit/aa9d0d1ca78d6adec3adfeecf3a706c7f9df81f2 Patch Third Party Advisory
Configurations

Configuration 1

cpe:2.3:a:nanopb_project:nanopb:*:*:*:*:*:*:*:*
cpe:2.3:a:nanopb_project:nanopb:*:*:*:*:*:*:*:*
cpe:2.3:a:nanopb_project:nanopb:*:*:*:*:*:*:*:*
Information

Published : 2020-02-04 03:15

Updated : 2020-02-06 06:51

NVD link : CVE-2020-5235

Mitre link : CVE-2020-5235

Products Affected
No products.
CWE
CWE-125

Out-of-bounds Read