Bug 2329982 (CVE-2024-53984) - CVE-2024-53984 nanopb: nanopb does not release memory on error return when using PB_DECODE_DELIMITED
Summary: CVE-2024-53984 nanopb: nanopb does not release memory on error return when us...
Keywords:
Status: NEW
Alias: CVE-2024-53984
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2329995 2329996 2329997 2329998
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-12-02 16:01 UTC by OSIDB Bzimport
Modified: 2024-12-02 17:51 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2024-12-02 16:01:20 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.