CVE-2014-1725

Description

The base64DecodeInternal function in wtf/text/Base64.cpp in Blink, as used in Google Chrome before 34.0.1847.116, does not properly handle string data composed exclusively of whitespace characters, which allows remote attackers to cause a denial of service (out-of-bounds read) via a window.atob method call.

References

Link	Tags
http://googlechromereleases.blogspot.com/2014/04/stable-channel-update.html
http://lists.opensuse.org/opensuse-updates/2014-05/msg00012.html	vendor advisory
http://security.gentoo.org/glsa/glsa-201408-16.xml	vendor advisory
http://www.debian.org/security/2014/dsa-2905	vendor advisory
https://code.google.com/p/chromium/issues/detail?id=357332
https://src.chromium.org/viewvc/blink?revision=170264&view=revision

Frequently Asked Questions

What is the severity of CVE-2014-1725?: CVE-2014-1725 has been scored as a medium severity vulnerability.
How to fix CVE-2014-1725?: To fix CVE-2014-1725, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2014-1725 being actively exploited in the wild?: It is possible that CVE-2014-1725 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~2% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.

Description

Category

CWE-20 – Improper Input Validation

References

Frequently Asked Questions