Fcambus

**Name of the Vulnerable Software and Affected Versions** md4c version 0.4.5 **Description** The issue allows attackers to trigger the use of uninitialized memory and cause a denial of service, such as an assertion failure, via a malformed Markdown document. This is due to a problem in the `md push block bytes` function in `md4c.c`. **Recommendations** For md4c version 0.4.5, consider avoiding the use of the `md push block bytes` function until a patch is available. As a temporary workaround, restrict the processing of malformed Markdown documents to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** peg-markdown version 0.4.14 **Description** The issue is related to a NULL pointer dereference in the `process raw blocks` function located in `markdown lib.c`. This problem only affects products that are no longer supported by the maintainer. **Recommendations** For peg-markdown version 0.4.14, consider restricting access to the `process raw blocks` function in `markdown lib.c` as a temporary workaround until a more permanent solution can be applied. However, since the products are no longer supported by the maintainer, at the moment, there is no information about a newer version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** FontForge version 20190801 **Description** The issue is a heap-based buffer overflow in the `Type2NotDefSplines()` function in `splinesave.c`. This occurs due to improper handling of data, leading to a potential overflow. **Recommendations** For FontForge version 20190801, as a temporary workaround, consider disabling the `Type2NotDefSplines()` function until a patch is available. 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** FontForge version 20190801 **Description** The issue is related to a use-after-free in the `SFD GetFontMetaData` function located in `sfd.c`. This indicates a memory management problem where memory is accessed after it has been freed, which can lead to unexpected behavior or crashes. No information is provided about the estimated number of potentially affected devices or real-world incidents where this issue was exploited. **Recommendations** For FontForge version 20190801, as a temporary workaround, consider restricting access to the `SFD GetFontMetaData` function in `sfd.c` until a patch is available. However, 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** Libspiro versions prior to 20190731 **Description** The issue is related to a stack-based buffer overflow in the `spiro to bpath0()` function, located in the spiro.c file. This overflow can potentially lead to an out-of-bounds write. **Recommendations** For Libspiro versions prior to 20190731, consider disabling the `spiro to bpath0()` function as a temporary workaround until a patch is available. Restrict access to the spiro.c module to minimize the risk of exploitation. Avoid using the affected function in critical operations until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Yabasic version 2.86.2 **Description** A heap-based buffer overflow issue exists in the `myformat` function within `function.c` due to a crafted BASIC source file. **Recommendations** For Yabasic version 2.86.2, 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** samurai version 0.7 **Description** The issue is related to a heap-based buffer overflow in the `canonpath` function within `util.c`, which can be triggered by a crafted build file. **Recommendations** For samurai version 0.7, 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** Yabasic version 2.86.1 **Description** A heap-based buffer overflow issue exists in the yylex() function, located in flex.c, which can be triggered by a crafted BASIC source file. **Recommendations** For Yabasic version 2.86.1, consider avoiding the use of crafted BASIC source files until a patch is available. As a temporary workaround, restrict the execution of potentially malicious BASIC source files to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** htmldoc version 1.9.7 **Description** The issue is related to a buffer overflow in the `hd strlcpy()` function, which can be exploited by a remote attacker to access confidential data, compromise data integrity, and cause a denial of service. This can occur when a crafted HTML document is processed. **Recommendations** For htmldoc version 1.9.7, consider disabling the `hd strlcpy()` function as a temporary workaround until a patch is available. Restrict access to the `render contents` function in `ps-pdf.cxx` to minimize the risk of exploitation. Avoid using crafted HTML documents that can trigger the buffer overflow in the `hd strlcpy()` function until the issue is resolved. 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** OpenDetex version 2.8.5 **Description** The issue is related to a Buffer Overflow in the TexOpen function in detex.l, caused by an incorrect use of sprintf. This vulnerability may allow a remote attacker to impact the confidentiality, integrity, and availability of protected information. **Recommendations** For OpenDetex version 2.8.5, consider applying a patch or fix that corrects the incorrect sprintf usage in the TexOpen function in detex.l to prevent the Buffer Overflow. 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** AdPlug version 2.3.1 **Description** The issue is related to multiple heap-based buffer overflows in the `Ca2mLoader::load()` function, located in the a2m.cpp file. **Recommendations** For AdPlug version 2.3.1, consider disabling the `Ca2mLoader::load()` function as a temporary workaround until a patch is available.

**Name of the Vulnerable Software and Affected Versions** AdPlug version 2.3.1 **Description** The issue is related to multiple heap-based buffer overflows in the `CmtkLoader::load()` function, located in `mtk.cpp`. **Recommendations** For AdPlug version 2.3.1, consider avoiding the use of the `CmtkLoader::load()` function until a patch is available. As a temporary workaround, restrict access to the `mtk.cpp` module to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** AdPlug version 2.3.1 **Description** The issue is related to multiple heap-based buffer overflows in the `CradLoader::load()` function, located in `rad.cpp`. **Recommendations** For AdPlug version 2.3.1, consider updating to a newer version that contains a fix for this issue, if available. As a temporary workaround, consider restricting access to the `CradLoader::load()` function until a patch is available.

**Name of the Vulnerable Software and Affected Versions** gdnsd versions prior to 2.4.3 gdnsd versions 3.x prior to 3.2.1 **Description** The issue is related to a stack-based buffer overflow in the set ipv6() function, which can be triggered by a long and malformed IPv6 address in zone data. **Recommendations** For versions prior to 2.4.3, update to version 2.4.3 or later. For versions 3.x prior to 3.2.1, update to version 3.2.1 or later.

**Name of the Vulnerable Software and Affected Versions** gdnsd versions 3.x before 3.2.1 **Description** The issue is related to a stack-based buffer overflow in the set ipv4() function, which can be triggered by a long and malformed IPv4 address in zone data. **Recommendations** For versions prior to 3.2.1, update to version 3.2.1 or later to resolve the issue.