CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2024-53984 – Nanopb does not release memory on error return when using PB_DECODE_DELIMITED
https://notcve.org/view.php?id=CVE-2024-53984
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. • https://github.com/nanopb/nanopb/commit/2b86c255aa52250438d5aba124d0e86db495b378 https://github.com/nanopb/nanopb/security/advisories/GHSA-xwqq-qxmw-hj5r • CWE-401: Missing Release of Memory after Effective Lifetime CWE-755: Improper Handling of Exceptional Conditions •
CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0CVE-2014-125106
https://notcve.org/view.php?id=CVE-2014-125106
Nanopb before 0.3.1 allows size_t overflows in pb_dec_bytes and pb_dec_string. Nanopb antes de v0.3.1 permite desbordamientos "size_t" en "pb_dec_bytes" y "pb_dec_string". • https://github.com/nanopb/nanopb/blob/master/CHANGELOG.txt https://github.com/nanopb/nanopb/commit/d2099cc8f1adb33d427a44a5e32ed27b647c7168 https://github.com/nanopb/nanopb/compare/nanopb-0.3.0...nanopb-0.3.1 • CWE-787: Out-of-bounds Write •
CVSS: 7.1EPSS: 0%CPEs: 2EXPL: 2CVE-2021-21401 – Invalid free() call in Nanopb
https://notcve.org/view.php?id=CVE-2021-21401
Nanopb is a small code-size Protocol Buffers implementation in ansi C. In Nanopb before versions 0.3.9.8 and 0.4.5, 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. This has been fixed in versions 0.3.9.8 and 0.4.5. • https://github.com/nanopb/nanopb/blob/c9124132a604047d0ef97a09c0e99cd9bed2c818/CHANGELOG.txt#L1 https://github.com/nanopb/nanopb/commit/e2f0ccf939d9f82931d085acb6df8e9a182a4261 https://github.com/nanopb/nanopb/issues/647 https://github.com/nanopb/nanopb/security/advisories/GHSA-7mv5-5mxh-qg88 • CWE-763: Release of Invalid Pointer or Reference •
CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 1CVE-2020-26243 – Memory leak in nanopb
https://notcve.org/view.php?id=CVE-2020-26243
Nanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, 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. This is fixed in versions 0.3.9.7 and 0.4.4. The following workarounds are available: 1) Set the option `no_unions` for the oneof field. • https://github.com/nanopb/nanopb/blob/2b48a361786dfb1f63d229840217a93aae064667/CHANGELOG.txt https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c https://github.com/nanopb/nanopb/issues/615 https://github.com/nanopb/nanopb/security/advisories/GHSA-85rr-4rh9-hhwh • CWE-20: Improper Input Validation CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •
CVSS: 9.8EPSS: 0%CPEs: 3EXPL: 0CVE-2020-5235 – Out-of-memory condition in Nanopb is potentially exploitable
https://notcve.org/view.php?id=CVE-2020-5235
There is a potentially exploitable out of memory condition In Nanopb before 0.4.1, 0.3.9.5, and 0.2.9.4. When nanopb is compiled with PB_ENABLE_MALLOC, the message to be decoded contains a repeated string, bytes or message field and realloc() runs out of memory when expanding the array nanopb can end up calling `free()` on a pointer value that comes from uninitialized memory. Depending on platform this can result in a crash or further memory corruption, which may be exploitable in some cases. This problem is fixed in nanopb-0.4.1, nanopb-0.3.9.5, nanopb-0.2.9.4. Se presenta una condición de falta de memoria explotable potencialmente en Nanopb versiones anteriores a 0.4.1, 0.3.9.5 y 0.2.9.4. • https://github.com/nanopb/nanopb/commit/45582f1f97f49e2abfdba1463d1e1027682d9856 https://github.com/nanopb/nanopb/commit/7b396821ddd06df8e39143f16e1dc0a4645b89a3 https://github.com/nanopb/nanopb/commit/aa9d0d1ca78d6adec3adfeecf3a706c7f9df81f2 https://github.com/nanopb/nanopb/security/advisories/GHSA-gcx3-7m76-287p • CWE-125: Out-of-bounds Read •