Skip to content
Fencer Intel
medium 6.5

CVE-2022-38475 json

An attacker could have written a value to the first element in a zero-length JavaScript array.

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

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

Summary

An attacker could have written a value to the first element in a zero-length JavaScript array. Although the array was zero-length, the value was not written to an invalid memory address. This vulnerability affects Firefox < 104.

Patch / fix

  • Mozilla Firefox 104
  • firefox Ubuntu 18.04 LTS 104.0+build3-0ubuntu0.18.04.1
  • firefox Ubuntu 20.04 LTS 104.0+build3-0ubuntu0.20.04.1
  • thunderbird Ubuntu 20.04 LTS 1:102.2.2+build1-0ubuntu0.20.04.1
  • thunderbird Ubuntu 22.04 LTS 1:102.2.2+build1-0ubuntu0.22.04.1

ubuntu advisories UBUNTU-CVE-2022-38475

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 104.0-1.1

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

Is CVE-2022-38475 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
partial
Assessed
last yr.

Exploit prediction

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

CVSS scores

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

Affected products

  • Mozilla Firefox

Classification

Weakness

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.