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.

• CVE ID
• CVE-2020-5235

• Assigner
• security-advisories@github.com

• Vulnerability Status
• Analyzed

• Published Version
• 2020-02-04T03:15:10

• Last Modified Date
• 2020-02-06T18:51:56

• Version
• 2.0

• Vector String
• AV:N/AC:L/Au:N/C:P/I:P/A:P

• Access Vector
• NETWORK

• Access Compatibility
• LOW

• Authentication
• NONE

• Confidentiality Impact
• PARTIAL

• Integrity Impact
• PARTIAL

• Availability Impact
• PARTIAL

• Base Score
• 7.5

• Severity
• HIGH

• Exploitability Score
• 10

• Impact Score
• 6.4

• Version
• 3.1

• Vector String
• CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

• Attack Vector
• NETWORK

• Attack Compatibility
• LOW

• Privileges Required
• NONE

• User Interaction
• NONE

• Scope
• UNCHANGED

• Confidentiality Impact
• HIGH

• Availability Impact
• HIGH

• Base Score
• 9.8

• Base Severity
• CRITICAL

• Exploitability Score
• 3.9

• Impact Score
• 5.9