Updates

A compilation of the latest information about viruses and worms, security issues and patches to rectify the same.

Internet Explorer Vulnerability

A vulnerability has been reported in Internet Explorer which is caused due to an error within the exception handling of script errors. It can be exploited to corrupt memory via an HTML document containing specially crafted JavaScript that triggers certain errors simultaneously. Once exploited, the vulnerability allows execution of arbitrary code. The problem can be taken care by applying the latest patches that are available on the Microsoft Web site.

ASPTicker “Password” SQL Injection Vulnerability

ASPTicker has been reported to have a vulnerability that can be exploited by malicious users to conduct SQL Injection attacks. The input passed to the “Password” form field parameter in ticker/admin.asp is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. By exploiting this vulnerability, malicious users can manipulate SQL queries by injecting arbitrary SQL code. The vulnerability can be resolved by editing the source code to ensure that input is properly sanitised.

tDiary Unspecified Ruby Code Execution Vulnerability

A vulnerability reported in tDiary can be exploited to compromise vulnerable systems. An unspecified error within the sanitation of input can be exploited to execute arbitrary Ruby code. Successful exploitation reportedly depends on the product’s configuration. As for now, the vulnerability has been reported in version 2.0.3, however, other versions may also be affected. Meanwhile, an update to version 2.0.4 resolves the vulnerability.

Cacti “cmd.php” Command Execution and SQL Injection

Three vulnerabilities have been reported in Cacti, which can be exploited to bypass certain security restrictions, manipulate data and compromise vulnerable systems. The vulnerabilities are:

1. The cmd.php script does not properly restrict access to command line usage and is installed in a Web-accessible location.

2. Input passed in the URL to cmd.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

Successful exploitation of both requires that register_argc_argv” is enabled.

3. The results from the SQL queries in the second instance in cmd.php are not properly sanitised before being used as shell commands. This can be exploited to inject arbitrary shellcommands.

The vulnerabilities are confirmed in version 0.8.6i. Other versions may also be affected.

The solution is to move the “cmd.php” script to a not Web-accessible path, and update other scripts accordingly. Then, edit the source code to ensure that input is properly sanitised.