Total 357 security vulnerabilities recorded for foxit software and firmware.
The application opened a PDF file containing an abnormal Unity 3D object. During parsing, the application incorrectly resolved a portion of the abnorm...
The input file does not need to be strictly in a structurally valid PDF format. Instead, after reviewing the content, the original document disguised ...
The PRC file header parsing logic trusts the constructed file structure description information, assumes that the underlying array contains elements a...
During the PRC parsing stage, there is a lack of boundary verification for the PRC entity index, which leads to an out-of-bounds read of the entity ar...
When the application opens a PDF and executes JavaScript, it performs abnormal operations on the list box field, and this operation is repeated after ...
The application opens a PDF containing an abnormal color space whose attributes reference a valid but semantically malformed function. The function's ...
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 ty...
An abnormal image object causes the renderer to enter the wrong processing branch. When converting the scan lines, an invalid image buffer pointer is ...
When the application opens a PDF file, during the process of JavaScript deleting pages and removing attachment annotations, it will cause the attachme...
The application opens a PDF, but the cloud-like appearance of the construction process lacks proper setting of an upper limit and consistency checks. ...
When the application opens a PDF and JavaScript resets the form fields, the script re-enters the interface. The underlying native object is damaged, b...
After the application opened the PDF file, the script first reset the annotation status, then triggered the reset form event by additional action. Dur...
When the application opens a PDF file and JavaScript writes annotation attributes, there is a lack of sufficient object type and argument checks. As a...
The application re-enters the document structure via field processing and deletes the current page, and then continues using the field objects obtaine...
When dealing with abnormally constructed objects, there is a lack of argument validation; JavaScript triggers signature verification, but the signatur...
When the application opens a PDF, traverses and builds the annotation elements related to hyperlinks, it fails to validate the abnormal annotation rel...
After JavaScript resetting the form, the synchronization process lacks re-entry protection and object lifecycle verification, resulting in the failure...
During the process of page opening and form formatting, a JavaScript reentrancy results in an inconsistent document status. Subsequently, with outdate...
The application opens the PDF, and JavaScript modifies the form. However, the related objects on the page lack complete lifecycle management and null ...
The application opens the PDF, and JavaScript performs operations on the page and the document, causing the page-related objects within the applicatio...
When the application opens a PDF file and JavaScript deletes the PDF fields, the subsequent logic still uses the old field pointers, resulting in inva...
The user-controllable executable files will be directly executed by high-privilege processes, allowing low-privilege users to have the opportunity to ...
After the application opened the PDF, JavaScript deleted the form field object. Subsequently, it attempted to access the invalid object, which caused ...
When the application opens a PDF and JavaScript modifies the properties of form fields, it causes the state of the underlying objects referenced by th...