# CVE-2022-0247: Write access to VMO data through copy-on-write in Fuchsia

> A local attacker can modify Virtual Memory Object data via copy-on-write snapshots, bypassing permissions to alter protected memory.

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2022
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-hf4w-4cm7-39h3

## What is CVE-2022-0247?

CVE-2022-0247 is a high-severity vulnerability in Google LLC Fuchsia, published on 25 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2022-0247?

It affects 1 product.


Products: Google Fuchsia.

## How do I fix CVE-2022-0247?

No fix has been published for CVE-2022-0247 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-0247 being exploited?

There is no known exploitation of CVE-2022-0247 in the wild and no public exploit code.

## Other vulnerabilities in Google LLC Fuchsia

- [CVE-2024-10604](https://insights.sbomify.com/CVE-2024-10604/): Identifiable Header Values In Fuchsia Leading To Tracking of The User (medium 6.9)
- [CVE-2021-22556](https://insights.sbomify.com/CVE-2021-22556/): Integer Overflow in Fuchsia Kernel (medium 5.3)
- [CVE-2022-0882](https://insights.sbomify.com/CVE-2022-0882/): Illegal access to Kernel log in Fuchsia (medium 5.3)
- [CVE-2021-22566](https://insights.sbomify.com/CVE-2021-22566/): Incorrect mapping of Executable bits in Fuchsia Kernel (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0247 and fix it if it is affected.

What it is: CVE-2022-0247 is a high-severity vulnerability in Google LLC Fuchsia, published on 25 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0247 in the wild and no public exploit code.

Affected product: Google LLC Fuchsia. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0247/ (Markdown: https://insights.sbomify.com/CVE-2022-0247/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0247
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0247
- OSV: https://osv.dev/vulnerability/CVE-2022-0247

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0247/
Summaries are generated and may contain mistakes; the official description above is the record.