Advisory

GHSA-7mv5-5mxh-qg88

Also known as: CVE-2021-21401, PYSEC-2021-432

Summary

nanopb vulnerable to invalid free() call with oneofs and PB_ENABLE_MALLOC

Details

Impact
Decoding a specifically formed message can cause invalid free() or realloc() calls if the message type contains an oneof field, and the oneof directly contains both a pointer field and a non-pointer field. If the message data first contains the non-pointer field and then the pointer field, the data of the non-pointer field is incorrectly treated as if it was a pointer value. Such message data rarely occurs in normal messages, but it is a concern when untrusted data is parsed.

Patches
Preliminary patch is available on git for 0.4.x and 0.3.x branches. The fix will be released in versions 0.3.9.8 and 0.4.5 once testing has been completed.

Workarounds
Following workarounds are available:

  • Set the option no_unions for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code.
  • Set the type of all fields inside the oneof to FT_POINTER. This ensures that the data contained inside the union is always a valid pointer.
  • Heap implementations that guard against invalid free() provide a partial mitigation. Depending on the message type, the pointer value may be attacker controlled and can be used to bypass heap protections.

References
Bug report: https://github.com/nanopb/nanopb/issues/647

For more information
If you have any questions or comments about this advisory, comment on the bug report linked above.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-08-30 18:45 UTC
Modified
2026-07-08 06:28 UTC

Affected packages and fixes

nanopb

PyPI · All systems

Affected

  • introduced 0.3.2, fixed 0.3.9.8 (ecosystem)

Fixed versions

0.3.9.8

Fix

  • Fixed version 0.3.9.8
    pip install --upgrade nanopb==0.3.9.8

nanopb

PyPI · All systems

Affected

  • introduced 0.4.0, fixed 0.4.5 (ecosystem)

Fixed versions

0.4.5

Fix

  • Fixed version 0.4.5
    pip install --upgrade nanopb==0.4.5

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences