Gap-Dev

Name of the Vulnerable Software and Affected Versions: ImageMagick versions prior to 7.1.2-0 Description: ImageMagick is free and open-source software used for editing and manipulating digital images. Versions prior to 7.1.2-0 experience infinite lines during a specific XMP file conversion command when writing. Recommendations: Update to version 7.1.2-0 or later.

**Name of the Vulnerable Software and Affected Versions** PDFio versions prior to 1.3.1 **Description** The issue concerns a denial of service (DOS) vulnerability in the TTF parser of the PDFio library. Maliciously crafted TTF files can cause the program to utilize 100% of the memory and enter an infinite loop, potentially leading to a heap-buffer-overflow vulnerability. This occurs due to the `nGroups` value extracted from the file, which, when altered, can cause the program to consume excessive memory and enter an infinite loop. The `read camp` function is specifically affected by this issue. Automated systems, including web servers using this library to convert PDF submissions into plaintext, are vulnerable to DOS attacks if an attacker uploads a malicious TTF file. **Recommendations** For versions prior to 1.3.1, upgrade to release version 1.3.1 to address the issue. As a temporary workaround, consider restricting the upload of TTF files or implementing additional validation checks on `nGroups` values to prevent excessive memory usage and infinite loops. Avoid using the `ttf.h` library until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** es5-ext versions prior to 0.10.63 **Description** The issue is related to the es5-ext package, which contains ECMAScript 5 extensions. Passing functions with very long names or complex default argument names into `function#copy` or `function#toStringTokens` may cause the script to stall. This can lead to a denial of service. **Recommendations** For versions prior to 0.10.63, update to version 0.10.63 or later to resolve the issue. As a temporary workaround, consider refraining from using the `function#copy` and `function#toStringTokens` utilities until a patch is applied.

**Name of the Vulnerable Software and Affected Versions** OpenEXR-viewer versions prior to 0.6.1 **Description** The issue is a memory overflow vulnerability in OpenEXR-viewer, a viewer for OpenEXR files with detailed metadata probing. This vulnerability is fixed in version 0.6.1. **Recommendations** For versions prior to 0.6.1, update to version 0.6.1 to resolve the issue. At the moment, there is no other information about additional mitigation measures.

**Name of the Vulnerable Software and Affected Versions** dot-diver versions prior to 1.0.2 **Description** The issue is related to a Prototype Pollution vulnerability in the `setByPath` function, which can lead to remote code execution (RCE). This vulnerability allows an attacker to modify object attributes, potentially enabling them to execute arbitrary code. The vulnerability is present in versions prior to 1.0.2 of the dot-diver library. **Recommendations** For versions prior to 1.0.2, upgrade to release 1.0.2 or later to address the Prototype Pollution vulnerability in the `setByPath` function. As a temporary workaround, consider restricting the use of the `setByPath` function until a patch is applied.

**Name of the Vulnerable Software and Affected Versions** get-func-name versions prior to 2.0.1 **Description** The issue is related to a regular expression denial of service (redos) vulnerability in the get-func-name module, which can lead to a denial of service when parsing malicious input. This vulnerability can be exploited when there is an imbalance in parentheses, resulting in excessive backtracking and increased CPU load and processing time. The vulnerability can be triggered using a specific input, such as `'t'.repeat(54773) + 't/function/i'`. The regex implementation in question is susceptible to excessive backtracking, leading to potential DoS attacks. **Recommendations** For versions prior to 2.0.1, upgrade to version 2.0.1 or later to address the issue. As a temporary workaround, consider restricting the use of the vulnerable `functionNameMatch` regex implementation until a patch is available. Avoid using the `functionNameMatch` regex with untrusted input until the issue is resolved. At the moment, there are no known workarounds for this vulnerability other than upgrading to a fixed version.