The application opens the PDF, and JavaScript modifies the form.
The application opens the PDF, and JavaScript modifies the form. However, the related objects on the page lack complete lifecycle management and null value validation; when the page state changes, the application continuously dereferences invalid objects, eventually leading to a crash.
· foxit pdf editor · foxit pdf reader—
The embedded JavaScript in the PDF deleted the pages, making the object invalid.
The embedded JavaScript in the PDF deleted the pages, making the object invalid. The application attempted to perform a write operation on the invalid pop-up annotations, resulting in the program crashing.
· foxit pdf editor · foxit pdf reader—
After the application opened the PDF, JavaScript deleted the form field object.
After the application opened the PDF, JavaScript deleted the form field object. Subsequently, it attempted to access the invalid object, which caused the application to crash.
· foxit pdf editor · foxit pdf reader—
Embedding JavaScript within a PDF file will cause the page to be deleted.
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.
· foxit pdf editor · foxit pdf reader—
When the application opens a PDF file, JavaScript uses the damaged field tree to trigger field traversal, resulting in the program holding an invalid form objec
When the application opens a PDF file, JavaScript uses the damaged field tree to trigger field traversal, resulting in the program holding an invalid form object when accessing the field property path. Eventually, the application crashes due to reading an invalid pointer.
· foxit pdf editor · foxit pdf reader—
When the application opens a PDF and JavaScript modifies the properties of form fields, it causes the state of the underlying objects referenced by the program
When the application opens a PDF and JavaScript modifies the properties of form fields, it causes the state of the underlying objects referenced by the program to become invalid. Eventually, it reads an illegal memory address, which leads to the crash of the application.
· foxit pdf editor · foxit pdf reader—
There is an abnormal annotation within the PDF that is referenced by other objects.
There is an abnormal annotation within the PDF that is referenced by other objects. When the application parses the PDF, it fails to perform proper type checking, ultimately causing the application to crash.
· foxit pdf editor · foxit pdf reader—
The application opens the PDF file.
The application opens the PDF file. JavaScript then rewrites the document to modify the page structure, resulting in the invalidation of the page objects. However, the thumbnails still use the invalid page objects, ultimately causing the application to crash.
· foxit pdf editor · foxit pdf reader—
When the application opens a PDF file, during the process of JavaScript deleting pages and removing attachment annotations, it will cause the attachment panel t
When the application opens a PDF file, during the process of JavaScript deleting pages and removing attachment annotations, it will cause the attachment panel to continue accessing invalid pointers, eventually leading to the application crashing.
· foxit pdf editor · foxit pdf reader—
An abnormal image object causes the renderer to enter the wrong processing branch.
An abnormal image object causes the renderer to enter the wrong processing branch. When converting the scan lines, an invalid image buffer pointer is used, resulting in the application crashing.
· foxit pdf editor · foxit pdf reader—