Skip to content
Fencer Intel
high 7.1

CVE-2022-42930 json

If two Workers were simultaneously initializing their CacheStorage, a data race could have occurred in the `ThirdPartyUtil` component.

published 3y ago modified 4mo ago also EUVD-2022-45986

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

If two Workers were simultaneously initializing their CacheStorage, a data race could have occurred in the `ThirdPartyUtil` component. This vulnerability affects Firefox < 106.

Patch / fix

  • Mozilla Firefox 106
  • firefox Ubuntu 18.04 LTS 106.0.2+build1-0ubuntu0.18.04.1
  • firefox Ubuntu 20.04 LTS 106.0.2+build1-0ubuntu0.20.04.1
  • thunderbird Ubuntu 20.04 LTS 1:102.4.2+build2-0ubuntu0.20.04.1
  • thunderbird Ubuntu 22.04 LTS 1:102.4.2+build2-0ubuntu0.22.04.1

ubuntu advisories UBUNTU-CVE-2022-42930

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • firefox-esr openSUSE Tumbleweed 128.5.1-1.1
  • MozillaFirefox openSUSE Tumbleweed 106.0-1.1

opensuse advisories openSUSE-SU-2024:14572-1openSUSE-SU-2024:12429-1

Is CVE-2022-42930 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Mozilla Firefox

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.