Skip to content
Fencer Intel
medium 4.3

CVE-2024-3838 json

Inappropriate implementation in Autofill in Google Chrome prior to 124.0.6367.60 allowed an attacker who convinced a user to install a mali…

published 2y ago modified 4mo ago also EUVD-2024-32407

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

Summary

Inappropriate implementation in Autofill in Google Chrome prior to 124.0.6367.60 allowed an attacker who convinced a user to install a malicious app to perform UI spoofing via a crafted app. (Chromium security severity: Medium)

Patch / fix

  • Google Chrome 124.0.6367.60
  • chromium Debian 12 124.0.6367.60-1~deb12u1
  • chromium Debian 14, Debian 13 124.0.6367.60-1

debian advisories DEBIAN-CVE-2024-3838

  • chromium openSUSE Tumbleweed 124.0.6367.201-1.1
  • opera openSUSE Leap 15.6 NonFree 110.0.5130.64-lp156.2.6.1
  • opera openSUSE Leap 15.5 NonFree 110.0.5130.23-lp155.3.45.1

opensuse advisories openSUSE-SU-2024:13953-1openSUSE-SU-2024:0156-1openSUSE-SU-2024:0128-1

Is CVE-2024-3838 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
2y ago

Exploit prediction

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

CVSS scores

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

Affected products

  • Google Chrome

Classification

Weakness
  • CWE-358 Improperly Implemented Security Check for Standard
Technology feeds

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.