InMail and InShop are susceptible to cross-site scripting vulnerabilities. These vulnerabilities occur due to a failure to properly sanitize user-supplied input before including it in dynamic web pages. An attacker can exploit these vulnerabilities by creating a malicious URI link that contains hostile HTML and script code. If a victim user follows this link, the hostile code may be rendered in their web browser, potentially allowing for theft of cookie-based authentication credentials or other attacks.
Java provides support for dynamic and static versioning when loading applets in the Java plug-in. This means that during the invocation of an applet, a user can request that a particular version of a plug-in be used to run the applet. The feature is accessible through various HTML tags that allow Java applets to be embedded in HTML documents, such as the EMBED, OBJECT, and APPLET tags. This feature presents a security weakness in that it may be abused to cause a previous version of a plug-in that is known to be prone to security vulnerabilities to be loaded in lieu of a more recent, fixed version. For this design flaw to pose a security threat, a vulnerable plug-in must either already be installed on the host computer or the user must manually install a version that is prone to security vulnerabilities. If a targeted version is not installed, the user may be prompted to install it. This weakness could result in a false sense of security, since the user may believe that installing an updated version will eliminate vulnerabilities in previous versions. Note that since this feature is supported in various browsers, the browsers themselves may be prone to the issue. Some browsers may not allow a Java plug-in that is no longer registered with the browser to run.
A handcrafted 'a.out' file can trigger a local denial-of-service condition, potentially resulting in a kernel panic. A memory-disclosure vulnerability affects only SMP computers with more than 4GB of memory, allowing a local attacker to access random pages of physical memory. Executing a specially crafted file results in a kernel oops and consuming file descriptors and memory.
This vulnerability in Microsoft Internet browser allows an attacker to crash the browser by performing an infinite JavaScript array sort operation. It is speculated that this vulnerability only leads to a denial of service and cannot be further exploited to execute arbitrary code, although this has not been confirmed.
A remote buffer overflow vulnerability affects the Open DC Hub. This issue is due to a failure of the application to properly validate the length of user-supplied strings prior to copying them into finite process buffers. An attacker may exploit this issue to execute arbitrary code with the privileges of the user that activated the vulnerable application. This may facilitate unauthorized access or privilege escalation.
JSPWiki is susceptible to a cross-site scripting vulnerability. This issue allows a remote attacker to create a malicious URI link that includes hostile HTML and script code. If the link is followed, the hostile code may be rendered in the web browser of the victim user, potentially leading to theft of authentication credentials or other attacks.
Zwiki is susceptible to a cross-site scripting vulnerability. This issue allows a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link is followed, the hostile code may be rendered in the web browser of the victim user.
A remote user can disclose directory listings by crafting a URI request containing directory traversal sequences. This allows the attacker to view the contents of a specified server directory located outside of the web root.
The Jabber Server is affected by multiple remote buffer overflow vulnerabilities. These vulnerabilities occur due to a lack of proper validation of user-supplied strings before copying them into finite process buffers. An attacker can exploit these vulnerabilities to execute arbitrary code on a computer with the privileges of the server process, potentially leading to unauthorized access or privilege escalation.
The vulnerabilities in SugarCRM arise from insufficient sanitization of user-supplied input. These vulnerabilities can be exploited by a remote attacker to carry out various attacks such as cross-site scripting, HTML injection, SQL injection, and directory traversal.
Services By CQR