Bug 445362 - (CVE-2008-2000) CVE-2008-2000 WebKit: DoS via JavaScript that calls document.write in an infinite loop
CVE-2008-2000 WebKit: DoS via JavaScript that calls document.write in an infi...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
http://nvd.nist.gov/nvd.cfm?cvename=C...
impact=low,reported=20080428,public=2...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-06 10:20 EDT by Tomas Hoger
Modified: 2016-03-04 07:28 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-05-06 10:26:38 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)

  None (edit)
Description Tomas Hoger 2008-05-06 10:20:37 EDT
Common Vulnerabilities and Exposures assigned an identifier CVE-2008-2000 to the following vulnerability:

Unspecified vulnerability in Apple Safari 3.1.1 allows remote attackers to cause a denial of service (application crash) via JavaScript code that calls document.write in an infinite loop.

Refences:
http://www.securityfocus.com/archive/1/archive/1/491192/100/0/threaded
http://es.geocities.com/jplopezy/pruebasafari3.html
http://www.frsirt.com/english/advisories/2008/1347
http://xforce.iss.net/xforce/xfdb/41985
Comment 1 Tomas Hoger 2008-05-06 10:26:38 EDT
This seems to be WebKit issue, not specific to Safari.  Malicious JavaScript can
cause huge memory and CPU resources consumption, leading to a browser crash.

We do not treat this kind of client application crashes as security issues, so
I'm closing this as notabug.  If this get addressed upstream (e.g. by
implementing some check that will allow user to interrupt JavaScript execution
after some time, same as gecko does), we'll follow shortly.

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