CVE-2022-3661: Insufficient data validation in Extensions
First published: Thu Aug 04 2022(Updated: )
Insufficient data validation in Extensions in Google Chrome prior to 107.0.5304.62 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted Chrome extension. (Chromium security severity: Low)
Credit: chrome-cve-admin@google.com Young Min Kim @ylemkimon CompSec Lab at Seoul National University
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome | <107.0.5304.62 | |
| Google Chrome | <107.0.5304.62 | 107.0.5304.62 |
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.
Reference Links
Peer vulnerabilities
(Found alongside the following vulnerabilities)
Frequently Asked Questions
What is the severity of CVE-2022-3661?
CVE-2022-3661 has a low severity rating as per Chromium security standards.
How do I fix CVE-2022-3661?
To mitigate CVE-2022-3661, ensure that you upgrade to Google Chrome version 107.0.5304.62 or later.
Who is affected by CVE-2022-3661?
CVE-2022-3661 affects Google Chrome versions prior to 107.0.5304.62.
What type of attack does CVE-2022-3661 allow?
CVE-2022-3661 allows a remote attacker to leak cross-origin data through a compromised Chrome extension.
What is the impact of CVE-2022-3661?
The impact of CVE-2022-3661 is the potential exposure of sensitive cross-origin data due to insufficient data validation.
- agent/references
- agent/type
- collector/nvd-api
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/weakness
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/description
- agent/author
- agent/title
- agent/severity
- agent/first-publish-date
- collector/chrome-releases
- agent/software-canonical-lookup
- agent/softwarecombine
- agent/event
- agent/trending
- agent/tags
- agent/source
- vendor/google
- canonical/google chrome