Closed Bug 499562 Opened 15 years ago Closed 13 years ago

ZipReader hangs when trying to extract into a target path containing a directory ending with ..

Categories

(Core Graveyard :: File Handling, defect)

x86
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 476541

People

(Reporter: georg, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1pre) Gecko/20090617 SeaMonkey/2.0b1pre
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-EN; rv:1.9.2a1pre) Gecko/20090619

ZipReader hangs with 100% CPU for one core when trying to extract into a target path containing a directory ending with two dots like /Volumnes/USBSTICK/mydir../target/

A target path like /Volumnes/USBSTICK/mydir../target/ causes ZipReader to hang when the directories mydir../target do not yet exist. Not teste, what happens, if they already exist. The problem occurs on MacOS X 10.5. May be other platforms affected too.



Reproducible: Always

Steps to Reproduce:
try to extract a zip file with target directory where to place the unzipped files containing at least one directory level ending with two dots
Actual Results:  
ZipReader hangs with 100% CPU. Unresponsive script warning never occurs, because not a script hangs but an XPCOM component hangs, so user has no chance to abort this.

Expected Results:  
creating the directories or throwing an error but not hanging
Georg, if you still see the hang on Mac, it is probably a duplicate of bug 	476541
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.