ChromeWeb browser · Google
CVE-2024-3838
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInappropriate 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)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceGoogle Chrome's Autofill feature had an implementation flaw prior to version 124.0.6367.60 that allowed a malicious application installed on a user's device to perform UI spoofing. An attacker would first need to convince the user to install a malicious app, which could then manipulate the Autofill UI to deceive users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 124.0.6367.60CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed Google Chrome versionOpen chrome://version in the Chrome address bar and note the version number displayed under 'Google Chrome' (the first line)Affected if The version number is lower than 124.0.6367.60 (for example, 124.0.6367.59 or any earlier version)
-
Verify the full version string includes the patch numberIn chrome://version, confirm the full version string such as 124.0.6367.59 or earlier. The second number (6367) and third number (59) must be less than 6367.60Affected if The version shows 124.0.6367.x where x is less than 60, or any version in the 124.0 branch before .60, or any version below 124 entirely
-
Confirm Autofill is enabled in Chrome settingsGo to Chrome Settings, click 'Autofill and passwords' (or 'Password Manager' in newer versions), then check if Autofill is turned on. Alternatively, navigate to chrome://settings/autofillAffected if Autofill is enabled and the Chrome version is below 124.0.6367.60 - the vulnerability only applies when Autofill is active
You are affected if Google Chrome is installed with a version lower than 124.0.6367.60 and the Autofill feature is enabled on your device.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped124.0.6367.60
Update Google Chrome to version 124.0.6367.60 or later. Users should avoid installing applications from untrusted sources to mitigate the prerequisite attack vector.
Chrome 124.0.6367.60 or later
- Open Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- If the version is earlier than 124.0.6367.60, Chrome will automatically check for and install updates
- Alternatively, download the latest stable Chrome from google.com/chrome and install it
- Restart Chrome after the update completes
- Verify the version is now 124.0.6367.60 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3838 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-3838 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data