Adobe Acrobat Reader PDF file DoS vulnerability =============================================== Title: Adobe Acrobat Reader PDF file DoS vulnerability HappyName: Too hunger for memory? Date: Sunday, April 11, 2004 Software: Adobe Acrobat Reader v4.0-v5.0 Vendor: Adobe Corporation Patch: Vendor notified, Look at "Vendor Status" section Author: Arman Nayyeri, arman-n[at]phreaker.net, http://www.4rman.com Severity: Low Description: ============ I found this vulnerability by hex editing a pdf file and changing a value to a large number. after executing the pdf file, the adobe acrobat reader displays a messagebox saying that the file is damaged and being repaired. But it takes too long to pdf to be repaired and it will allocate a large amount of memory to itself, so it will cause a DoS in memory. In most cases windows will freez, because there is no memory for loading any program, a messageboxes telling virtual memory too low will be displayed. I don't have any info about the value in the pdf, what it will do, or anything else! this code in pdf will cause dos in acrobat reader: "/UseOutlines ?>> ?endobj?[big number]" in the exploit I use : "/UseOutlines ?>> ?endobj?9999999". As the pdf files can be automatically loaded by web pages this vulnerability becomes more dangerous. Exploit: ======== I provide a page that loads pdf file by embed tag, it will cause the memory to fills up. WARNING!!!!! This DoS will cause serious system instability, please save your work before loading this page, you may need to restart your computer! Here is the page that loads pdf: http://www.4rman.com/exploits/pdfdos.htm Download pdf: http://www.4rman.com/exploits/thanks.pdf (BIG ONE) http://www.4rman.com/exploits/thanks2.pdf (SMALL ONE) please, take a look at my website too! http://www.4rman.com Exploit Tested On ================= Adobe Acrobat Reader 4.0 Adobe Acrobat Reader 5.0 Vendor Status ============= Adobe notified about 3 month ago. they request a sample and the description, I send it. but I don't recieve any response. Special Thanks ============== Special thanks to god. Do I discover more vulnerabilities? =================================== Maybe!(heh) Disclaimer: =========== Arman Nayyeri is not responsible for the misuse of the information provided in this advisory. The opinions expressed are my own and not of any company. In no event shall the author be liable for any damages whatsoever arising out of or in connection with the use or spread of this advisory. Any use of the information is at the user's own risk. ~~~~~~~~~~~~~~ and sorry for my bad english, Arman Nayyeri From Iran http://www.4rman.com
