CVE Vulnerability Catalog

Plate prior to 53.3.2 has a vulnerability in @platejs/docx-io that fetches remote image URLs while converting attacker-controlled HTML through htmlToDocxBlob in a server-side environment. The converter can make requests to internal network resources and include the fetched image bytes in the generated DOCX, allowing server-side request forgery with response disclosure.

Link Preview JS prior to 4.0.4 has a vulnerability in the resolveDNSHost mitigation that validates one resolved IP address but fetches the original hostname, allowing an attacker-controlled DNS server to return a public address during validation and a loopback or internal address during the final connection, bypassing SSRF protection.

NanaZip from version 1.0.88.0 until stable 6.0.1698.0 and preview 6.5.1742.0 has a vulnerability in the Lz4Decode function that rejects only a zero return from LZ4_decompress_safe, while malformed input produces a negative error value. The negative int is converted to unsigned SizeT, leading to out-of-bounds read and potential data leak or crash.

LangBot version 4.10.7 and earlier has a vulnerability that allows any authenticated user to add or change an STDIO MCP server configuration without an adequate authorization boundary. An attacker can configure commands and arguments that are executed as a subprocess on the LangBot server, enabling arbitrary command execution with LangBot service privileges.

deepmerge-ts prior to 8.0.0 has a vulnerability in the deepmerge, deepmergeCustom, deepmergeInto, and deepmergeIntoCustom APIs that do not track visited objects when recursively merging. When two input values contain self-references at the same property path, the merge logic repeatedly revisits the same pair until Node.js raises RangeError: Maximum call stack size exceeded, causing process crash.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing APNG files. The issue is due to lack of proper validation of user-supplied data, leading to an integer overflow before buffer allocation. User interaction is required, such as opening a malicious file.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing TIF files. The issue is due to lack of proper validation of user-supplied data, leading to an integer overflow before buffer allocation. User interaction is required, such as opening a malicious file.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing TIF files. The issue is due to lack of proper validation of the length of user-supplied data before copying it to a heap-based buffer, leading to a heap-based buffer overflow. User interaction is required, such as opening a malicious file.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing SGI files. The issue is due to lack of proper validation of user-supplied data, leading to an integer overflow before writing to memory. User interaction is required, such as opening a malicious file.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing TIF files. The issue is due to lack of proper validation of user-supplied data, leading to an integer overflow before buffer allocation. User interaction is required, such as opening a malicious file.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing TIF files. The issue is due to lack of proper validation of user-supplied data, leading to an integer overflow before buffer allocation. User interaction is required, such as opening a malicious file.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing TIF files. The issue is due to lack of proper validation of the length of user-supplied data before copying it to a stack-based buffer, leading to a stack-based buffer overflow. User interaction is required, such as opening a malicious file.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing TIF files. The issue is due to lack of proper validation of the length of user-supplied data before copying it to a heap-based buffer, leading to a heap-based buffer overflow. User interaction is required, such as opening a malicious file.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing PSD files. The issue is due to lack of proper validation of user-supplied data, leading to an integer overflow before buffer allocation. User interaction is required, such as opening a malicious file.

This vulnerability allows a remote attacker to execute arbitrary code in GIMP when parsing HDR files. The issue is due to lack of proper validation of user-supplied data, leading to an integer overflow before buffer allocation. User interaction is required, such as opening a malicious file.

Use-After-Free vulnerability in GStreamer rtpsbcdepay allows remote code execution. Lack of validating object existence before operations leads to use-after-free. An attacker can leverage this to execute code in the context of the current process.

Heap-based buffer overflow in GStreamer PNG file parsing allows remote code execution. Lack of proper length validation before copying data to heap buffer leads to overflow. User interaction is required, such as visiting a malicious page or opening a malicious file.

Stack-based buffer overflow in GStreamer OGG file parsing allows remote code execution. Lack of proper length validation before copying data to stack buffer leads to overflow. User interaction is required, such as visiting a malicious page or opening a malicious file.

Heap-based buffer overflow in GStreamer MRF file parsing allows remote code execution. Lack of proper length validation before copying data to heap buffer leads to overflow. User interaction is required, such as visiting a malicious page or opening a malicious file.

Out-of-bounds write in GStreamer MRF file parsing allows remote code execution. Lack of proper validation of user-supplied data leads to write past the end of an allocated buffer. User interaction is required, such as visiting a malicious page or opening a malicious file.