PDF Viewer vulnerabilities

When opening a PDF file, during JavaScript-based deletion of pages and attachment annotations, the attachment panel accesses invalid pointers, causing the application to crash.

The vulnerability in a PDF viewing application occurs when JavaScript resets form fields, causing re-entry into the interface and damaging the native object. The application fails to validate the object before calling a function, leading to a crash.

The vulnerability in the PDF viewing application stems from incomplete lifecycle management and null value validation of objects. JavaScript modifies the form, and when the page state changes, the application repeatedly dereferences invalid objects, eventually causing a crash.

The vulnerability in a PDF viewing application occurs when JavaScript performs operations on the page and document, causing page-related objects to lose synchronization. The renderer still trusts the outdated page count, leading to out-of-bounds access and application crash.

The vulnerability in the PDF viewing application occurs when JavaScript modifies form field properties, causing the state of underlying objects referenced by the program to become invalid. This eventually leads to reading an illegal memory address and crashing the application.

Embedding JavaScript within a PDF file will cause the page to be deleted. Subsequent scripts will continue to access the relevant properties of the document view, eventually leading to the crash of the application.

The vulnerability occurs when the application opens a PDF file, and JavaScript rewrites the document, modifying the page structure and invalidating page objects. Thumbnails still use these invalid objects, ultimately causing the application to crash.