Description
The Autofill feature in Google Chrome before 19.0.1084.46 does not properly restrict field values, which allows remote attackers to cause a denial of service (UI corruption) and possibly conduct spoofing attacks via vectors involving long values.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Tumbleweed | chromium | 55.0.2883.75-3.1 | openSUSE-SU-2024:12948-1, openSUSE-SU-2024:10171-1 |
Advisories 2
- openSUSE-SU-2024:10171-1 chromedriver-55.0.2883.75-3.1 on GA media SUSE / openSUSE Security Updates · Feb 4, 2026
- openSUSE-SU-2024:12948-1 ungoogled-chromium-113.0.5672.92-1.1 on GA media SUSE / openSUSE Security Updates · Feb 4, 2026
References
- GLSA-201205-03 vendor-advisory
- google-autofilled-code-execution(75590) vdb-entry
- openSUSE-SU-2012:0656 vendor-advisory
- 1027067 vdb-entry
- http://code.google.com/p/chromium/issues/detail?id=118374
- http://googlechromereleases.blogspot.com/2012/05/stable-channel-update.html
- 53540 vdb-entry
- oval:org.mitre.oval:def:15256 vdb-entry signature