Suyue Guo

An issue exists where unauthenticated attackers can cause server memory exhaustion by sending a compressed Erlang external term within a gRPC message body. The `GRPC.Codec.Erlpack.decode/2` function passes the message body to `:erlang.binary to term/2`, which inflates compressed terms fully without a size limit. Because the server's `max body size` limit only tracks compressed bytes, a request using `Content-Type: application/grpc+erlpack` can force the server to allocate memory significantly larger than the actual request body. This occurs because the codec's type checks are only performed after the term has been decoded.

Name of the Vulnerable Software and Affected Versions Multiple / Unspecified Products (affected versions not specified) Description The application does not properly validate the lifetime and validity of internal view cache pointers after JavaScript changes the document zoom and page state. When a script modifies the zoom property and then triggers a page change, the original view object may be destroyed while stale pointers are still kept and later dereferenced, which under crafted JavaScript and document structures can lead to a use-after-free condition and potentially allow arbitrary code execution. Recommendations At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions The product name cannot be determined. (affected versions not specified) Description The application does not validate the presence of required appearance (AP) data before accessing stamp annotation resources. When a PDF contains a stamp annotation missing its AP entry, the code continues to dereference the associated object without a prior null or validity check, which can trigger a null pointer dereference and crash the application, resulting in denial of service. Recommendations At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions Multiple / Unspecified Products (affected versions not specified) Description The application does not detect or guard against cyclic PDF object references while handling JavaScript in PDF. When pages and annotations are crafted that reference each other in a loop, passing the document to APIs (e.g., `SOAP`) that perform deep traversal can cause uncontrolled recursion, stack exhaustion, and application crashes. Recommendations At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: PDF-XChange Editor (affected versions not specified) Description: This issue allows remote attackers to execute arbitrary code on affected installations of PDF-XChange Editor. User interaction is required to exploit this, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of App objects due to the lack of validating the existence of an object prior to performing operations on it. An attacker can leverage this to execute code in the context of the current process. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

This issue allows remote attackers to disclose sensitive information on affected installations. It requires user interaction, such as visiting a malicious page or opening a malicious file. The flaw exists within the handling of util objects, where an attacker can trigger a read past the end of an allocated object by performing actions in JavaScript. This can be leveraged in conjunction with other issues to execute arbitrary code in the context of the current process.

This issue allows remote attackers to execute arbitrary code on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of Doc objects due to the lack of validation of an object's existence before performing operations on it. An attacker can leverage this to execute code in the context of the current process.

This issue allows remote attackers to execute arbitrary code on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of Collab objects, specifically due to a buffer read past the end of an allocated buffer when performing actions in JavaScript. This can be leveraged to execute code in the context of the current process.

This issue allows remote attackers to execute arbitrary code on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the `submitForm` method, where an attacker can trigger a read past the end of an allocated buffer by performing actions in JavaScript, allowing code execution in the context of the current process.

This issue allows remote attackers to disclose sensitive information on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of `Doc` objects. By performing actions in JavaScript, an attacker can trigger a read past the end of an allocated object. This can be leveraged in conjunction with other issues to execute arbitrary code in the context of the current process.

This issue allows remote attackers to execute arbitrary code on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the `AFSpecial KeystrokeEx` method due to the lack of validating the existence of an object prior to performing operations on it, which can result in a memory corruption condition. An attacker can leverage this to execute code in the context of the current process.

This issue allows remote attackers to disclose sensitive information on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of ADBC objects, allowing an attacker to trigger a read past the end of an allocated object by performing actions in JavaScript. This can be leveraged in conjunction with other issues to execute arbitrary code in the context of the current process.

This issue allows remote attackers to disclose sensitive information on affected installations. User interaction is required to exploit this, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of the `AFSpecial KeystrokeEx` method due to the lack of validating the existence of an object prior to performing operations on it. An attacker can leverage this, in conjunction with other issues, to execute arbitrary code in the context of the current process.

This issue allows remote attackers to disclose sensitive information on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of Doc objects, specifically when the application handles certain JavaScript actions, allowing an attacker to trigger a read past the end of an allocated object. This can be leveraged in conjunction with other issues to execute arbitrary code in the context of the current process.

This issue allows remote attackers to execute arbitrary code on affected installations. User interaction is required, where the target must visit a malicious page or open a malicious file. The flaw exists within the handling of Doc objects, specifically when the application fails to properly validate allocation boundaries for objects when handling certain JavaScripts. By performing actions in JavaScript, an attacker can trigger a read past the end of an allocated object, potentially leading to remote code execution in the context of the current process.