Jetson Nano, Jetson Nano 2GB: Incorrect Permission Assignment for Critical Resource
CVE-2022-21819 is a high-severity incorrect permission assignment for critical resource vulnerability in Jetson Nano, Jetson Nano 2GB from NVIDIA, with a CVSS 3.1 base score of 7.6 out of 10. It can be exploited with physical access to the device by an unauthenticated attacker, without any action from a user. Affected Jetson Nano, Jetson Nano 2GB versions: All 32.x versions prior to 32.7.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.41% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Jetson Linux to 32.7.1 or a later version.
- Read the advisory on nvidia.custhelp.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NVIDIA | Jetson Nano, Jetson Nano 2GB | All 32.x versions prior to 32.7.1 | Not stated |
| NVIDIA | Jetson Linux | 32.1 up to, but not including, 32.7.1 | 32.7.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- PhysicalThe attacker must physically touch the device.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.6 | High | CNA (nvidia.com) |
| CVSS 3.1 | 7.6 | High | NVD |
| CVSS 2.0 | 4.6 | Medium | NVD |
Official description
NVIDIA distributions of Jetson Linux contain a vulnerability where an error in the IOMMU configuration may allow an unprivileged attacker with physical access to the board direct read/write access to the entire system address space through the PCI bus. Such an attack could result in denial of service, code execution, escalation of privileges, and impact to data integrity and confidentiality. The scope impact may extend to other components.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Incorrect Permission Assignment for Critical Resource vulnerabilities
- 7.8 High severity
- 9.1 Critical severity
- 7.3 High severity
- 7.8 High severity
- 7.8 High severity
- 4.3 Medium severity
Spotted an error? Tell us.