nanopb
Affected
- introduced
0.3.2, fixed0.3.9.7, introduced0.4.0, fixed0.4.4(ecosystem)
Fixed versions
0.3.9.7, 0.4.4
Fix
- Fixed version
0.3.9.7pip install --upgrade nanopb==0.3.9.7 - Fixed version
0.4.4pip install --upgrade nanopb==0.4.4
Advisory
Also known as: CVE-2020-26243, GHSA-85rr-4rh9-hhwh
Memory leak in Nanopb
Impact
Decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed.
Patches
Preliminary patch is available on git and problem will be patched in versions 0.3.9.7 and 0.4.4 once testing has been completed.
Workarounds
Following workarounds are available:
no_unions for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code.FT_POINTER. This way the whole submessage will be dynamically allocated and the problematic code is not executed.References
Bug report: https://github.com/nanopb/nanopb/issues/615
For more information
If you have any questions or comments about this advisory, comment on the bug report linked above.
High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
0.3.2, fixed 0.3.9.7, introduced 0.4.0, fixed 0.4.4 (ecosystem)0.3.9.7, 0.4.4
0.3.9.7pip install --upgrade nanopb==0.3.9.70.4.4pip install --upgrade nanopb==0.4.4Fix 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
Source: PyPA Advisory Database · CC BY 4.0