Memory Leak Affecting nanopb package, versions <0.4.9.1-1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.41% (35th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-NANOPB-8453767
  • published4 Dec 2024
  • disclosed2 Dec 2024

Introduced: 2 Dec 2024

CVE-2024-53984  (opens in a new tab)
CWE-401  (opens in a new tab)
CWE-755  (opens in a new tab)

How to fix?

Upgrade Debian:unstable nanopb to version 0.4.9.1-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nanopb package and not the nanopb package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Nanopb is a small code-size Protocol Buffers implementation. When the compile time option PB_ENABLE_MALLOC is enabled, the message contains at least one field with FT_POINTER field type, custom stream callback is used with unknown stream length. and the pb_decode_ex() function is used with flag PB_DECODE_DELIMITED, then the pb_decode_ex() function does not automatically call pb_release(), like is done for other failure cases. This could lead to memory leak and potential denial-of-service. This vulnerability is fixed in 0.4.9.1.