CVE Vulnerability Catalog

The application opened a PDF file containing an abnormal Unity 3D object. During parsing, the application incorrectly resolved a portion of the abnormal object as a pointer and used it as a valid address, ultimately causing the application to crash.

When opening a PDF with embedded JavaScript, the application performs abnormal operations on a list box field, repeated after form reset. The application fails to properly validate form objects and their internal dictionary pointers, leading to an illegal pointer read and application crash.

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.

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 the PDF-opening application stems from missing upper limit and consistency checks during the construction process. This leads to out-of-bounds array access, ultimately 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.

A vulnerability in a PDF viewing application causes a crash after opening a PDF file. The script resets the annotation state and triggers a form reset event, leading to access of invalid objects and application crash.

The vulnerability in the PDF viewing application is due to insufficient object type and argument checks when JavaScript writes annotation attributes. This corrupts the internal annotation structure and causes the application to crash during resource release.

The vulnerability involves the application re-entering the document structure during field processing, which deletes the current page. The application then continues using field objects obtained before deletion, causing an illegal read and crash.

A vulnerability in the signature plugin causes missing argument validation when copying abnormally constructed objects. JavaScript triggers signature verification, but the plugin does not validate the copied abnormal string, leading to application crash.

When opening a PDF, the application fails to validate abnormal annotation relationships and field combinations related to hyperlinks, causing internal objects to enter an invalid state. During destruction, an invalid pointer write occurs, crashing the application.

After JavaScript resets the form, the synchronization process lacks re-entry protection and object lifecycle verification, causing the control pointer to fail during traversal. The application continues to dereference the failed pointer, 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 occurs when the application opens a PDF file and JavaScript deletes the PDF fields, but the subsequent logic still uses the old field pointers, resulting in invalid pointer references and causing the application to crash.

The vulnerability allows low-privilege users to execute arbitrary executable files with NT AUTHORITY\SYSTEM privileges, enabling privilege escalation.

After opening a PDF file, the application executed JavaScript that deleted a form field object. Subsequently, it attempted to access the invalid object, causing the application to 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.

A heap buffer overflow in BitmapScaleBitmaps in libXfont2 before 2.0.8 due to an overflowing 32-bit size could be used by attackers able to access the X Server to execute code within the X server context.

A vulnerability in Xorg server and Xwayland allows local attackers with an X connection to trigger a Heap Use-After-Free via the CommonMakeCurrent() function, which may point to potentially reallocated memory.

A vulnerability in Xorg server and Xwayland before versions 21.2.24 and 24.1.13 allows local attackers with an X connection to cause a heap buffer overflow via the SetFont function using crafted PCX fonts. Missing glyph boundary checks lead to buffer overflow.