Closed Bug 240524 Opened 20 years ago Closed 20 years ago

Bitmap Memory Allocation Error Lets Remote Users Cause All Available Memory to Be Consumed

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 240369

People

(Reporter: staffjp, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040414
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040414

I tried the "new" denial of service bug that was claimed at

http://www.securitytracker.com/alerts/2004/Apr/1009746.html

Microsoft Internet Explorer Bitmap Memory Allocation Error Lets Remote Users
Cause All Available Memory to Be Consumed 

Tried the above IE DOS vulnerability on a mid march daily of Mozilla 1.7 and all
available memory was consumed instantly and the swap file was growing at the
maximum allowable rate.

Tried the same test url on todays 04/14/04 daily and about 190MB was used
instantly and the swap file began growing,
the browser appears to still operate to some degree, as I could close it.


Reproducible: Always
Steps to Reproduce:
1.  Prepare to end task on Mozilla
2.  Load that website noted above.
3.  Watch memory be consumed using whatever tool you like, I used Task Manager.

Actual Results:  
On the mid march daily, all memory was consumed instantly and the swap file
was growing at the maximum allowable rate.

On today's daily, about 190MB was used instantly and the swap file began growing,
the browser appears to still operate to some degree, as I could close it.
not a security issue, just mozilla using much memory

*** This bug has been marked as a duplicate of 240369 ***
Group: security
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Summary: Bitmap Memory Allocation Error Lets Remote Users Cause All Available Memory to Be Consumed → Bitmap Memory Allocation Error Lets Remote Users Cause All Available Memory to Be Consumed
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.