Bug 640353 (CVE-2010-3116) - CVE-2010-3116 webkit: memory corruption with MIME types
Summary: CVE-2010-3116 webkit: memory corruption with MIME types
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2010-3116
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 640382 640385 640386
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-05 16:05 UTC by Vincent Danen
Modified: 2019-09-29 12:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-07 07:02:57 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0177 normal SHIPPED_LIVE Moderate: webkitgtk security update 2011-01-25 17:07:15 UTC

Description Vincent Danen 2010-10-05 16:05:14 UTC
Common Vulnerabilities and Exposures assigned an identifier CVE-2010-3116 to
the following vulnerability:

Google Chrome before 5.0.375.127 does not properly process MIME types, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.

References:

* Chrome Bug: http://code.google.com/p/chromium/issues/detail?id=50515
* Chrome Bug: http://code.google.com/p/chromium/issues/detail?id=51835
* Bugzilla: https://bugs.webkit.org/show_bug.cgi?id=43147
* Bugzilla: https://bugs.webkit.org/show_bug.cgi?id=43888
* Trac: http://trac.webkit.org/changeset/64293
* Trac: http://trac.webkit.org/changeset/65280

This issue has been corrected in WebKitGTK 1.2.5.

Comment 1 Vincent Danen 2010-10-05 17:19:14 UTC
Created webkitgtk tracking bugs for this issue

Affects: fedora-all [bug 640382]

Comment 3 errata-xmlrpc 2011-01-25 17:07:42 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2011:0177 https://rhn.redhat.com/errata/RHSA-2011-0177.html


Note You need to log in before you can comment on or make changes to this bug.