This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When creating a Bodhi update request, use the bodhi submission link noted in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the Bodhi notes field when available. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs]
Use the following update submission link to create the Bodhi request for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. IMPORTANT: ensure that the "Close bugs when update is stable" option remains checked. Bodhi update submission link: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1101056,1101057
ARM specific, this can not affect Fedora i686 and x86_64 architectures. It may affect armv7hl, I haven't investigated further.
Found the upstream fix here: https://codereview.chromium.org/219473002 I would assume this affects all fedora versions of v8 since it affects all Google V8 before 3.25.28.16. And I see that Fedora 21 is only at version v8-3.14.5.10-14.fc21.armv7hl. Would need to be backported.
Can a fix for this be shipped?
Can an update be pushed for this package?
I think I know how to backport the fix, but since it only applies to ARM, I cannot test to see if it resolves it. Eric, can you?
Hmm... I don't seem to have any ARM devices around any more. Let me see if I can find a tester. By the way, this was reduced from Important to Moderate so I've reduced the impact on the ticket accordingly.
It's possible I could set this up on my VM environment at home: https://fedoraproject.org/wiki/Architectures/ARM/HowToQemu Might be enough to test this (ARM VM with libvirt).
Id be happy to test on an ARM device, if you can give me a patch to test and a set of steps to try to reproduce the issue.
v8-3.14.5.10-18.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/v8-3.14.5.10-18.fc22
v8-3.14.5.10-18.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/v8-3.14.5.10-18.fc21
v8-3.14.5.10-18.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/v8-3.14.5.10-18.fc20
Please test that. I went ahead and pushed it as an update because of the minimal risk envelope (it's unlikely I made anything _worse_ on ARM), but I'll wait to hear confirmation that it resolves the CVE before I push to stable.
Package v8-3.14.5.10-18.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing v8-3.14.5.10-18.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-6845/v8-3.14.5.10-18.fc21 then log in and leave karma (feedback).
Just to note, this update is waiting for someone to explicitly test it before I will push it to stable.
(In reply to Jared Smith from comment #10) > Id be happy to test on an ARM device, if you can give me a patch to test and > a set of steps to try to reproduce the issue. Jared are you going to be able to test this?
I tried the regress-358057.js from the upstream commit on arm03-packager00.cloud.fedoraproject.org and it runs without asserting with both v8-1:3.14.5.10-17.fc21.armv7hl and v8-1:3.14.5.10-18.fc21.armv7hl. It doesn't seem to break anything though.
I assume that is the same regress-358057.js from the upstream google code I linked to above.
v8-3.14.5.10-18.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
v8-3.14.5.10-18.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
v8-3.14.5.10-18.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.