Bug 1086116 (CVE-2014-1721)

Summary:	CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116
Product:	[Other] Security Response	Reporter:	Murray McAllister <mmcallis>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	abaron, aortega, apevec, ayoung, bdunne, bgollahe, bkearney, bleanhar, cbillett, ccoleman, chrisw, cpelland, dajohnso, dallan, dclarizi, dmcphers, drieden, gkotton, gmccullo, jdetiber, jfrey, jialiu, jkeck, jokerman, jomara, jorton, jprause, jrafanie, jvlcek, katello-bugs, kseifried, lhh, lmeyer, lpeer, markmc, mburns, mmaslano, mmccomas, mmccune, mmcgrath, obarenbo, rbryant, rhos-maint, sclewis, tcallawa, tchollingsworth, thrcka, tjay, tomckay, tomspur, vdanen, xlecauch, yeylon
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-04 14:03:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1086118, 1086119
Bug Blocks:	1086126

Description Murray McAllister 2014-04-10 07:13:46 UTC

Common Vulnerabilities and Exposures assigned an identifier CVE-2014-1721 to
the following vulnerability:

Name: CVE-2014-1721
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-1721
Assigned: 20140129
Reference: http://googlechromereleases.blogspot.com/2014/04/stable-channel-update.html
Reference: https://code.google.com/p/chromium/issues/detail?id=350434
Reference: https://code.google.com/p/v8/source/detail?r=19834

Google V8, as used in Google Chrome before 34.0.1847.116, does not
properly implement lazy deoptimization, which allows remote attackers
to cause a denial of service (memory corruption) or possibly have
unspecified other impact via crafted JavaScript code, as demonstrated
by improper handling of a heap allocation of a number outside the
Small Integer (aka smi) range.

This is possibly impact moderate or low with the way v8 is used in Red Hat products and Fedora. Investigation ongoing.

Comment 1 Murray McAllister 2014-04-10 07:16:50 UTC

Created v8 tracking bugs for this issue:

Affects: fedora-all [bug 1086118]
Affects: epel-6 [bug 1086119]

Comment 2 Tomas Hoger 2014-06-16 14:18:17 UTC

Most of the patch is applicable to v8 3.14.  However, the test case form upstream commit does not reproduce any issue with 3.14.  It requires removal of %SetAllocationTimeout which is not supported in that version.  It does not seem such change should break the test.

Comment 3 Tomas Hoger 2014-09-04 14:03:43 UTC

Not reproducible with the other test case from the other bug:

https://code.google.com/p/chromium/issues/detail?id=350434#c12

Assuming this is not needed for 3.14.