CVE-2022-34480
First published: Tue Jun 28 2022(Updated: )
Within the <code>lg_init()</code> function, if several allocations succeed but then one fails, an uninitialized pointer would have been freed despite never being allocated. This vulnerability affects Firefox < 102.
Credit: security@mozilla.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Firefox | <102 | 102 |
| Firefox | <102.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-34480?
CVE-2022-34480 is classified as a moderate severity vulnerability affecting Firefox versions prior to 102.
How do I fix CVE-2022-34480?
To fix CVE-2022-34480, update Firefox to version 102 or later.
What type of vulnerability is CVE-2022-34480?
CVE-2022-34480 is a memory corruption vulnerability resulting from an uninitialized pointer being freed.
Which versions of Firefox are affected by CVE-2022-34480?
CVE-2022-34480 affects all versions of Firefox prior to 102.
Can CVE-2022-34480 lead to exploitation?
Yes, CVE-2022-34480 could potentially allow an attacker to execute arbitrary code.
- agent/type
- agent/first-publish-date
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/mozilla-advisory
- agent/software-canonical-lookup-request
- source/Mozilla
- agent/software-canonical-lookup
- collector/nvd-index
- agent/softwarecombine
- vendor/mozilla
- canonical/firefox