Input validation error in Google Chrome - CVE-2013-2916
Published: October 2, 2013 / Updated: August 10, 2020
Google Chrome
Detailed vulnerability description
The vulnerability allows a remote non-authenticated attacker to manipulate data.
Blink, as used in Google Chrome before 30.0.1599.66, allows remote attackers to spoof the address bar via vectors involving a response with a 204 (aka No Content) status code, in conjunction with a delay in notifying the user of an attempted spoof.
How to mitigate CVE-2013-2916
Sources
- http://googlechromereleases.blogspot.com/2013/10/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2013-10/msg00002.html
- http://lists.opensuse.org/opensuse-security-announce/2013-12/msg00002.html
- http://lists.opensuse.org/opensuse-updates/2014-01/msg00042.html
- http://www.debian.org/security/2013/dsa-2785
- https://code.google.com/p/chromium/issues/detail?id=281256
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A18968
- https://src.chromium.org/viewvc/blink?revision=157196&view=revision