Mancha

**Name of the Vulnerable Software and Affected Versions** rsyslog versions prior to 8.4.2 sysklogd version 1.5 and earlier **Description** The issue affects the rsyslog package in Gentoo Linux and can lead to a disruption in the confidentiality, integrity, and availability of protected information. It is caused by an integer overflow when parsing PRI values, which can be exploited remotely. By sending a specially crafted message, an attacker can cause the service to crash, resulting in a denial of service. **Recommendations** For rsyslog versions prior to 8.4.2, update to version 8.4.2 or later to resolve the issue. For sysklogd version 1.5 and earlier, consider upgrading to a version later than 1.5 to mitigate the risk. As a temporary workaround, consider restricting access to the `PRI` parsing functionality until a patch is available.

**Name of the Vulnerable Software and Affected Versions** KDE-Workspace versions 4.10.5 and earlier **Description** The issue arises from improper handling of the return value of the glibc 2.17 crypt and pw encrypt functions. This allows remote attackers to cause a denial of service, resulting in a NULL pointer dereference and crash. The attack can be initiated via an invalid salt or a DES or MD5 encrypted password when FIPS-140 is enabled, targeting KDM, or through an invalid password to KCheckPass. **Recommendations** For KDE-Workspace versions 4.10.5 and earlier, consider updating to a version that properly handles the return value of the glibc crypt and pw encrypt functions to prevent the denial of service. 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** cyrus-sasl versions prior to 2.1.26 **Description** The issue is related to the improper handling of a NULL value returned by the crypt function, as implemented in glibc 2.17 and later. This can be exploited by remote attackers to cause a denial of service, resulting in thread crashes and consumption. The exploitation can occur via an invalid salt or, when FIPS-140 is enabled, through DES or MD5 encrypted passwords, triggering a NULL pointer dereference. **Recommendations** For versions prior to 2.1.26, update to version 2.1.26 or later to resolve the issue. As a temporary workaround, consider restricting access to the crypt function to minimize the risk of exploitation.