https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 13:34:23 +0000 https://cve.radiocsirt.org/vuln/certfr-2021-avi-240 certfr-2021-avi-240 https://cve.radiocsirt.org/vuln/certfr-2021-avi-240 https://cve.radiocsirt.org/vuln/euvd-2026-36461 EUVD-2026-36461 https://cve.radiocsirt.org/vuln/euvd-2026-36461 https://cve.radiocsirt.org/vuln/fkie_cve-2020-5235 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-5235 https://cve.radiocsirt.org/vuln/ghsa-6f6v-26gj-6crp <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-6f6v-26gj-6crp https://cve.radiocsirt.org/vuln/gsd-2020-5235 gsd-2020-5235 https://cve.radiocsirt.org/vuln/gsd-2020-5235 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11074-1 <p>libprotobuf-nanopb0-0.4.5-1.3 on GA media</p> <p>libprotobuf-nanopb0-0.4.5-1.3 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11074-1