Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1077136 - (CVE-2014-1704) CVE-2014-1704 v8: multiple vulnerabilities fixed in Google Chrome version 33.0.1750.149
CVE-2014-1704 v8: multiple vulnerabilities fixed in Google Chrome version 33....
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20140114,reported=2...
: Security
Depends On: 1077137 1077138 1139698
Blocks: 1077139 1139716
  Show dependency treegraph
 
Reported: 2014-03-17 06:32 EDT by Murray McAllister
Modified: 2017-09-08 08:08 EDT (History)
50 users (show)

See Also:
Fixed In Version: v8 3.23.17.18
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-10-30 08:59:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:1744 normal SHIPPED_LIVE Moderate: v8314-v8 security update 2014-10-30 12:08:15 EDT

  None (edit)
Description Murray McAllister 2014-03-17 06:32:38 EDT
Common Vulnerabilities and Exposures assigned an identifier CVE-2014-1704 to
the following vulnerability:

Multiple unspecified vulnerabilities in Google V8 before 3.23.17.18,
as used in Google Chrome before 33.0.1750.149, allow attackers to
cause a denial of service or possibly have other impact via unknown
vectors.

http://googlechromereleases.blogspot.com/2014/03/stable-channel-update_11.html

https://code.google.com/p/chromium/issues/detail?id=328202
https://code.google.com/p/v8/source/detail?r=18564

https://code.google.com/p/chromium/issues/detail?id=345715
https://code.google.com/p/v8/source/detail?r=19614

https://code.google.com/p/chromium/issues/detail?id=349079
https://code.google.com/p/v8/source/detail?r=19668
Comment 1 Murray McAllister 2014-03-17 06:36:59 EDT
Created v8 tracking bugs for this issue:

Affects: fedora-all [bug 1077137]
Affects: epel-6 [bug 1077138]
Comment 2 T.C. Hollingsworth 2014-03-18 18:39:44 EDT
(In reply to Murray McAllister from comment #0)
> Reference: https://code.google.com/p/v8/source/detail?r=18564

Will backport this one.

> Reference: https://code.google.com/p/v8/source/detail?r=19614
> Reference: https://code.google.com/p/v8/source/detail?r=19668

These both involve operations with smis (which is v8 parlance for "small integers", something more commonly known to programmers as "fixnums") that aren't present in v8 3.14.
Comment 3 Fedora Update System 2014-04-02 05:05:48 EDT
v8-3.14.5.10-7.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 4 Fedora Update System 2014-04-15 11:32:45 EDT
v8-3.14.5.10-7.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 5 Fedora Update System 2014-04-15 19:31:39 EDT
v8-3.14.5.10-7.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 8 Garth Mollett 2014-10-08 01:54:17 EDT
Statement:

Red Hat Product Security has rated this issue as having Low security impact in Red Hat Enterprise Linux OpenStack Platform. This issue is not currently planned to be addressed in a future security update.
Comment 9 errata-xmlrpc 2014-10-30 08:09:22 EDT
This issue has been addressed in the following products:

  Red Hat Software Collections 1 for Red Hat Enterprise Linux 7
  Red Hat Software Collections 1 for Red Hat Enterprise Linux 6.5 EUS
  Red Hat Software Collections 1 for Red Hat Enterprise Linux 6.4 EUS
  Red Hat Software Collections 1 for Red Hat Enterprise Linux 6

Via RHSA-2014:1744 https://rhn.redhat.com/errata/RHSA-2014-1744.html

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