CVE-2022-36320
First published: Tue Jul 26 2022(Updated: )
Mozilla developers and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 102. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.
Credit: security@mozilla.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Firefox | <103 | 103 |
| Firefox | <103.0 | |
| <103.0 |
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-36320?
CVE-2022-36320 has a moderate severity rating due to potential memory corruption issues.
How do I fix CVE-2022-36320?
To remediate CVE-2022-36320, users should update to Firefox version 103 or later.
What can be exploited in CVE-2022-36320?
CVE-2022-36320 may potentially be exploited to run arbitrary code on affected systems.
What versions of Firefox are affected by CVE-2022-36320?
CVE-2022-36320 affects Firefox versions prior to 103.
Who reported the issues in CVE-2022-36320?
The issues in CVE-2022-36320 were reported by Mozilla developers and the Mozilla Fuzzing Team.
- agent/type
- agent/first-publish-date
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/description
- agent/event
- agent/trending
- agent/source
- collector/mozilla-advisory
- agent/software-canonical-lookup-request
- source/Mozilla
- agent/software-canonical-lookup
- collector/nvd-index
- agent/tags
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- vendor/mozilla
- canonical/firefox