CVE-2022-46879
Last modified
CVE-2022-46879 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. Mozilla developers and community members Lukas Bernhard, Gabriele Svelto, Randell Jesup, and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 107. 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. EPSS estimates a 0.64% chance of exploitation in the next 30 days.
Description
Mozilla developers and community members Lukas Bernhard, Gabriele Svelto, Randell Jesup, and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 107. 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. This vulnerability affects Firefox < 108.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Mozilla | Firefox | < 108.0 |
References
- https://www.mozilla.org/security/advisories/mfsa2022-51/Vendor Advisory
- https://www.mozilla.org/security/advisories/mfsa2022-51/Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-46879?
How severe is CVE-2022-46879?
How do I fix CVE-2022-46879?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-46872An attacker who compromised a content process could have par…8.6
- CVE-2022-46873Because Firefox did not implement the <code>unsafe-hashes</c…8.8
- CVE-2022-46874A file with a long filename could have had its filename trun…8.8
- CVE-2022-46875The executable file warning was not presented when downloadi…6.5
- CVE-2022-46877By confusing the browser, the fullscreen notification could …4.3
- CVE-2022-46878Mozilla developers Randell Jesup, Valentin Gosu, Olli Pettay…8.8
- CVE-2022-4688Improper Authorization in GitHub repository usememos/memos p…8.8
- CVE-2022-46880A missing check related to tex units could have led to a use…6.5
- CVE-2022-46881An optimization in WebGL was incorrect in some cases, and co…8.8
- CVE-2022-46882A use-after-free in WebGL extensions could have led to a pot…9.8
- CVE-2022-46883Mozilla developers Gabriele Svelto, Yulia Startsev, Andrew M…8.8
- CVE-2022-46884A potential use-after-free vulnerability existed in SVG Imag…8.8
Are you affected by CVE-2022-46879?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
