Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
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 nounions 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 FTPOINTER. This ensures that the data contained inside the union is always a valid pointer. Heap…
Recommended action: Upgrade to 0.4.5 or 0.3.9.8 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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: Set the option nounions for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code. Set the type of the submessage field inside oneof to FTPOINTER. This way the whole submessage will be dynamically allocated and the problematic code is not executed. Use an arena allocator for nanopb, to make sure all memory can be released afterwards. References Bug report: https://github.com/nanopb/nanopb/issues/615 For more…
Recommended action: Upgrade to 0.4.4 or 0.3.9.7 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.