Closed tchollingsworth closed 11 years ago
If v8/v8@eea2c15 is the fix then master has it and v0.10 doesn't. I don't mind landing the patch but on a threat scale of 1 to 10, this ranks maybe a 2.
I can't view the chromium bug report. Apparently it's still under embargo?
Yeah, a remote DoS for chrome is just a local DoS for node, but "unspecified other impacts" make us itchy, so this is already backported in Fedora.
I'm not sure why the bug is still embargoed, the CVE is public and this was mentioned in the Chrome release notes.
Okay, landed in v0.10 in 6b92a71. Thanks for reporting it.
Common Vulnerabilities and Exposures assigned an identifier CVE-2013-2882 to the following vulnerability:
Name: CVE-2013-2882 URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2882 Assigned: 20130411 Reference: http://googlechromereleases.blogspot.com/2013/07/stable-channel-update_30.html Reference: https://code.google.com/p/chromium/issues/detail?id=260106 Fedora tracking bug: https://bugzilla.redhat.com/show_bug.cgi?id=991116
Google V8, as used in Google Chrome before 28.0.1500.95, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that leverage "type confusion."
Looks like the relevant v8 commit is: v8/v8@eea2c15ffe
Any idea whether this affects v0.10 or v0.11?