CVE-2010-3114

Description

The text-editing implementation in Google Chrome before 5.0.375.127, and webkitgtk before 1.2.6, does not check a node type before performing a cast, which has unspecified impact and attack vectors related to (1) DeleteSelectionCommand.cpp, (2) InsertLineBreakCommand.cpp, or (3) InsertParagraphSeparatorCommand.cpp in WebCore/editing/.

10.0

CVSS

Severity: Critical

CVSS 2.0 •

EPSS 0.62%

Vendor Advisory mandriva.com Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory google.com Vendor Advisory blogspot.com

Affected: n/a n/a

References

Link	Tags
http://www.mandriva.com/security/advisories?name=MDVSA-2011:039	third party advisory vendor advisory
http://www.vupen.com/english/advisories/2010/2722	vdb entry third party advisory
http://trac.webkit.org/changeset/63773	third party advisory patch
http://googlechromereleases.blogspot.com/2010/08/stable-channel-update_19.html	vendor advisory
http://www.ubuntu.com/usn/USN-1006-1	third party advisory vendor advisory
http://secunia.com/advisories/41856	third party advisory
http://www.vupen.com/english/advisories/2011/0216	vdb entry third party advisory
http://secunia.com/advisories/43086	third party advisory
http://code.google.com/p/chromium/issues/detail?id=49628	issue tracking patch vendor advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11577	vdb entry third party advisory signature
http://www.securityfocus.com/bid/44201	vdb entry third party advisory
http://www.redhat.com/support/errata/RHSA-2011-0177.html	third party advisory vendor advisory
http://www.vupen.com/english/advisories/2011/0552	vdb entry third party advisory
https://bugzilla.redhat.com/show_bug.cgi?id=628035	issue tracking third party advisory

Frequently Asked Questions

What is the severity of CVE-2010-3114?: CVE-2010-3114 has been scored as a critical severity vulnerability.
How to fix CVE-2010-3114?: To fix CVE-2010-3114, 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-2010-3114 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2010-3114 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.