CVE-2022-0247: Write access to VMO data through copy-on-write in Fuchsia
First published: Fri Feb 25 2022(Updated: )
An issue exists in Fuchsia where VMO data can be modified through access to copy-on-write snapshots. A local attacker could modify objects in the VMO that they do not have permission to. We recommend upgrading past commit d97c05d2301799ed585620a9c5c739d36e7b5d3d or any of the listed versions.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Fuchsia | <2022-01-03 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the vulnerability ID of this issue?
The vulnerability ID of this issue is CVE-2022-0247.
What is the severity level of CVE-2022-0247?
CVE-2022-0247 has a severity level of high.
What is the affected software?
The affected software is Google Fuchsia.
How can an attacker exploit CVE-2022-0247?
A local attacker can exploit CVE-2022-0247 by modifying objects in the VMO that they do not have permission to.
How can I fix CVE-2022-0247?
To fix CVE-2022-0247, we recommend upgrading to a version past commit d97c05d2301799ed585620a9c5c739d36e7b5d3d or any of the listed versions.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/last-modified-date
- agent/remedy
- agent/severity
- agent/weakness
- agent/references
- agent/author
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- vendor/google
- canonical/google fuchsia