CVE-2022-20385
Publication date 13 September 2022
Last updated 24 July 2024
Ubuntu priority
a function called 'nla_parse', do not check the len of para, it will check nla_type (which can be controlled by userspace) with 'maxtype' (in this case, it is GSCAN_MAX), then it access polciy array 'policy[type]', which OOB access happens.Product: AndroidVersions: Android SoCAndroid ID: A-238379819
Status
| Package | Ubuntu Release | Status |
|---|---|---|
| libnl3 | ||
| 22.04 LTS jammy |
Not affected
|
|
| 20.04 LTS focal |
Not affected
|
|
| 18.04 LTS bionic |
Not affected
|
|
| 16.04 LTS xenial |
Not affected
|
|
| 14.04 LTS trusty |
Not affected
|
Notes
mdeslaur
This is an Android CVE, as of 2022-09-16, there is no indication what the issue is, what the fix is, and if the issue affects the libnl3 package in Ubuntu.
ccdm94
Looking at the libnl3 code and at the CVE description, a few of the mentioned functions, types and variables can be found: function 'nla_parse' does exist, and 'nla_type' exists as well. The 'policy[type]' access is also done. However, there seems to be no variable called 'para'. Therefore, looking only at the CVE description and at the only advisory made available by Android, it is not possible to determine, as of 2022-10-11, if libnl3 is vulnerable in any Ubuntu release. Upstream also has not released any commits that seems to be related to this issue, and, therefore, no current fix for libnl3 is avaiable if it is vulnerable.
mdeslaur
no indication this affects Ubuntu, marking as not-affected
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score |
9.8 · Critical
|
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity impact | High |
| Availability impact | High |
| Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |