CVE-2020-26243
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2020-26243
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2020-26243.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2020-26243
- Aliases
- Related
- Published
- 2020-11-25T17:15:12Z
- Modified
- 2025-01-08T10:29:49.933413Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- [none]
- Details
-
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_unionsfor the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code. 2) Set the type of the submessage field inside oneof toFT_POINTER. This way the whole submessage will be dynamically allocated and the problematic code is not executed. 3) Use an arena allocator for nanopb, to make sure all memory can be released afterwards. - References
-
- https://github.com/nanopb/nanopb/security/advisories/GHSA-85rr-4rh9-hhwh
- https://github.com/nanopb/nanopb/issues/615
- https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c
- https://github.com/nanopb/nanopb/blob/2b48a361786dfb1f63d229840217a93aae064667/CHANGELOG.txt
- https://security-tracker.debian.org/tracker/CVE-2020-26243
Affected packages
Debian:11 / nanopb
Package
- Name
- nanopb
- Purl
- pkg:deb/debian/nanopb?arch=source
Debian:12 / nanopb
Package
- Name
- nanopb
- Purl
- pkg:deb/debian/nanopb?arch=source
Debian:13 / nanopb
Package
- Name
- nanopb
- Purl
- pkg:deb/debian/nanopb?arch=source
Git / github.com/nanopb/nanopb
Affected ranges
- Type
- GIT
- Repo
- https://github.com/nanopb/nanopb
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixedFixed