Nicolas Ruff

**Name of the Vulnerable Software and Affected Versions** kdenetwork-kopete-devel version 4.10.5 kdenetwork-kopete version 4.10.5 kdenetwork-krdc version 4.10.5 kdenetwork-kget-libs version 4.10.5 kdenetwork-krfb-libs version 4.10.5 kdenetwork-kdnssd version 4.10.5 kdenetwork-fileshare-samba version 4.10.5 kdenetwork-devel version 4.10.5 kdenetwork-common version 4.10.5 kdenetwork-krdc-devel version 4.10.5 kdenetwork-kget version 4.10.5 kdenetwork-krdc-libs version 4.10.5 kdenetwork-kopete-libs version 4.10.5 kdenetwork-krfb version 4.10.5 kdenetwork-debuginfo version 4.10.5 **Description** The issue is related to multiple vulnerabilities in the kdenetwork package, which can lead to a disruption of confidentiality, integrity, and availability of protected information. These vulnerabilities can be exploited remotely by an attacker who has passed the authentication procedure. The vulnerabilities are associated with various components of the kdenetwork package, including kdenetwork-kopete-devel, kdenetwork-kopete, kdenetwork-krdc, kdenetwork-kget-libs, kdenetwork-krfb-libs, kdenetwork-kdnssd, kdenetwork-fileshare-samba, kdenetwork-devel, kdenetwork-common, kdenetwork-krdc-devel, kdenetwork-kget, kdenetwork-krdc-libs, kdenetwork-kopete-libs, kdenetwork-krfb, and kdenetwork-debuginfo. The rfbProcessClientNormalMessage function in libvncserver/rfbserver.c in LibVNCServer 0.9.9 and earlier does not properly handle attempts to send a large amount of ClientCutText data, which allows remote attackers to cause a denial of service (memory consumption or daemon crash) via a crafted message that is processed by using a single unchecked malloc. **Recommendations** For kdenetwork-kopete-devel version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-kopete version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-krdc version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-kget-libs version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-krfb-libs version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-kdnssd version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-fileshare-samba version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-devel version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-common version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-krdc-devel version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-kget version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-krdc-libs version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-kopete-libs version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-krfb version 4.10.5, update to a newer version to mitigate the risk. For kdenetwork-debuginfo version 4.10.5, update to a newer version to mitigate the risk. As a temporary workaround, consider disabling the `rfbProcessClientNormalMessage` function until a patch is available.

**Name of the Vulnerable Software and Affected Versions** kdenetwork-kopete-devel version 4.10.5 kdenetwork-krdc version 4.10.5 kdenetwork-kopete version 4.10.5 kdenetwork-kget-libs version 4.10.5 kdenetwork-krfb-libs version 4.10.5 kdenetwork-kdnssd version 4.10.5 kdenetwork-common version 4.10.5 kdenetwork-fileshare-samba version 4.10.5 kdenetwork-devel version 4.10.5 kdenetwork-kget version 4.10.5 kdenetwork-krdc-libs version 4.10.5 kdenetwork-krdc-devel version 4.10.5 kdenetwork-krfb version 4.10.5 kdenetwork-debuginfo version 4.10.5 LibVNCServer version 0.9.9 and earlier **Description** The issue is related to multiple vulnerabilities in various packages of the kdenetwork suite, which can lead to a disruption of confidentiality, integrity, and availability of protected information. These vulnerabilities can be exploited remotely by an attacker who has passed the authentication procedure. Additionally, a vulnerability in the LibVNCServer library can cause a denial of service (divide-by-zero error and server crash) via a zero value in the scaling factor in a PalmVNCSetScaleFactor or SetScale message. **Recommendations** For kdenetwork-kopete-devel version 4.10.5, restrict access to the vulnerable components to minimize the risk of exploitation. For kdenetwork-krdc version 4.10.5, consider disabling the remote access functionality until a patch is available. For kdenetwork-kopete version 4.10.5, avoid using the vulnerable features until the issue is resolved. For kdenetwork-kget-libs version 4.10.5, restrict access to the vulnerable libraries to minimize the risk of exploitation. For kdenetwork-krfb-libs version 4.10.5, consider disabling the vulnerable libraries until a patch is available. For kdenetwork-kdnssd version 4.10.5, restrict access to the vulnerable components to minimize the risk of exploitation. For kdenetwork-common version 4.10.5, avoid using the vulnerable features until the issue is resolved. For kdenetwork-fileshare-samba version 4.10.5, restrict access to the vulnerable components to minimize the risk of exploitation. For kdenetwork-devel version 4.10.5, consider disabling the vulnerable development tools until a patch is available. For kdenetwork-kget version 4.10.5, restrict access to the vulnerable components to minimize the risk of exploitation. For kdenetwork-krdc-libs version 4.10.5, avoid using the vulnerable libraries until the issue is resolved. For kdenetwork-krdc-devel version 4.10.5, consider disabling the vulnerable development tools until a patch is available. For kdenetwork-krfb version 4.10.5, restrict access to the vulnerable components to minimize the risk of exploitation. For kdenetwork-debuginfo version 4.10.5, avoid using the vulnerable debugging tools until the issue is resolved. For LibVNCServer version 0.9.9 and earlier, update to a newer version to mitigate the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** LibVNCServer versions 0.9.9 and earlier **Description** The issue is related to the HandleRFBServerMessage function in LibVNCServer, which is associated with an error in designating the full screen. Exploitation of this issue may allow a remote attacker to access confidential data, compromise its integrity, and cause a denial of service. The vulnerability can be triggered by a remote VNC server specifying a large screen size in certain messages, potentially leading to application crashes or arbitrary code execution. **Recommendations** For LibVNCServer versions 0.9.9 and earlier, consider disabling the HandleRFBServerMessage function as a temporary workaround until a patch is available. Restrict access to the LibVNCServer library to minimize the risk of exploitation. Avoid using the library with untrusted VNC servers 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: Microsoft Windows 2000 SP4 Description: The issue concerns the Remote Installation Service (RIS) in Microsoft Windows, which uses a TFTP server allowing anonymous access. This allows remote attackers to upload and overwrite arbitrary files, potentially gaining privileges on systems that use RIS. Recommendations: For Microsoft Windows 2000 SP4, consider disabling the RIS service or restricting access to the TFTP server to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Microsoft Office versions 2000 SP3, Office XP SP3, Office 2003 SP1 and SP2 Microsoft Office for Mac versions 2004, X Description: The issue allows user-assisted attackers to execute arbitrary code via a PowerPoint document with a malformed record, which triggers memory corruption. It is a remote code execution vulnerability that can be exploited by constructing a specially crafted PowerPoint file. Recommendations: For Microsoft Office 2000 SP3, update to a version that is not affected by this issue. For Microsoft Office XP SP3, update to a version that is not affected by this issue. For Microsoft Office 2003 SP1 and SP2, update to a version that is not affected by this issue. For Microsoft Office 2004 for Mac, update to a version that is not affected by this issue. For Microsoft Office X for Mac, update to a version that is not affected by this issue.