CVE-2022-20203
In multiple locations of the nanopb library, there is a possible way to corrupt memory when...
In multiple locations of the nanopb library, there is a possible way to corrupt memory when decoding untrusted protobuf files. This could lead to local escalation of privilege,with no additional execution privileges needed. User interaction is not needed for exploitation.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
In multiple locations of the nanopb library, there is a possible way to corrupt memory when decoding untrusted protobuf files. This could lead to local escalation of privilege,with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
CVE-2022-20203- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 4.6 Medium
AV:L/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-787
- Updated
- 2026-11-02
CVE List No score
In multiple locations of the nanopb library, there is a possible way to corrupt memory when decoding untrusted protobuf files. This could lead to local escalation of privilege,with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
CVE-2022-20203- Updated
- 2026-11-02
EUVDEUVD-2022-25463 No score
In multiple locations of the nanopb library, there is a possible way to corrupt memory when decoding untrusted protobuf files. This could lead to local escalation of privilege,with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
EUVD-2022-25463- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-8jvx-gwwj-j77h
In multiple locations of the nanopb library, there is a possible way to corrupt memory when...
In multiple locations of the nanopb library, there is a possible way to corrupt memory when decoding untrusted protobuf files. This could lead to local escalation of privilege,with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
GHSA-8jvx-gwwj-j77h- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2022-20203
In multiple locations of the nanopb library, there is a possible way to corrupt memory when decoding untrusted protobuf files. This could lead to local escalation of privilege,with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
UBUNTU-CVE-2022-20203- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
nanopbUbuntu:Pro:20.04:LTS |
All versions, plus listed versions 0.4.1-10.4.1-1ubuntu0.1~esm1 |
None known |
nanopbUbuntu:22.04:LTS |
All versions, plus listed versions 0.4.4-20.4.5-10.4.5-2 |
None known |
nanopbUbuntu:24.04:LTS |
All versions, plus listed versions 0.4.7-20.4.7-30.4.8-1 |
None known |
nanopbUbuntu:25.10 |
All versions, plus listed versions 0.4.9.1-1 |
None known |
nanopbUbuntu:26.10 |
All versions, plus listed versions 0.4.9.1-1build10.4.9.1-2 |
None known |
nanopbUbuntu:26.04:LTS |
All versions, plus listed versions 0.4.9.1-10.4.9.1-1build1 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2022-20203 is a high vulnerability (CVSS 7.8) in Google Android, published June 15, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.13%, the 2nd percentile. No source names a fixed version.