Closed Bug 1174283 Opened 11 years ago Closed 10 years ago

Malicious Instagram Java Script Hang and Freeze Vulnerability

Categories

(Core :: JavaScript Engine, defect)

36 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gopalraha, Unassigned)

Details

(Keywords: csectype-dos, hang)

Attachments

(5 files)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150605094246 Steps to reproduce: 1. Open the Mozilla Firefox Browser and access the Instagram (https://www.instagram.com). 2. After Scrolling the Hang of Instagram in Mozilla Firefox browser Scroll is locked and browser cannot be responded. 3. This Hang is Due to Unresponsive 'FEEDPAGE.js' Java Script. 4. Mozilla Firefox Browser cannot be responded due to Instagram JS Hang. 5. CPU load Goes to 100% load due to Instagram JS Hang. 6. More than 500 MB RAM is Consumed by Mozilla Firefox Browser due to Instagram JS Hang. For More Information See the Screenshots Attachments Actual results: The Mozilla Firefox is under Hang and Freezes also CPU load Goes to 100% load and More than 500 MB RAM is Consumed by Mozilla Firefox Browser. Expected results: This may continue the Blue Screen errors due to the Kernel Crash of Windows Operating System due to this errors causes DDOS attacks on Windows OS due to this JS venerability.
Version: 38 Branch → 36 Branch
Group: core-security
Keywords: csectype-dos, hang
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/45.0 Nightly 45.0a1 Build ID: 20151214030220 and Firefox 42.0 Gopal, Thank you for reporting this. Are you still having the issue in the latest version ?
Component: Untriaged → JavaScript Engine
Flags: needinfo?(gopalraha)
Product: Firefox → Core
User Agent Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0 Version 46.0a1 Build ID 20160114030207 Channel nightly I do not reproduce this issue. The CPU usage is less than 5%. Closing this as incomplete due to inactivity and lack of response from the reporter. Please feel free to reopen the bug if the issue still reproduces on a current build. Thanks
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Correcting the status as works for me: The issue is not reproducible for me in the given steps. If the issue still reproduces consistently on a current build, please feel free to reopen it. Appreciated.
Resolution: INCOMPLETE → WORKSFORME
Flags: needinfo?(gopalraha)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: