Thursday, December 20, 2012

Log Analyzer 3.6.0 - Cross Site Scripting Vulnerability

Title:
======
Log Analyzer 3.6.0 - Cross Site Scripting Vulnerability


Date:
=====
2012-12-20


References:
===========
http://www.vulnerability-lab.com/get_content.php?id=792
Vendor: http://loganalyzer.adiscon.com/security-advisories/loganalyzer-cross-site-scripting-vulnerability-in-oracle_query-paramater


VL-ID:
=====
792


Common Vulnerability Scoring System:
====================================
1.5


Introduction:
=============
LogAnalyzer is part of Adiscon`s MonitorWare line of monitoring applications. It runs both under Windows and Unix/Linux.
The database can be populated by MonitorWare Agent, WinSyslog or EventReporter on the Windows side and by rsyslog on
the Unix/Linux side. LogAnalyzer itself is free, GPLed software (as are some other members of the product line).

(Copy of the Vendor Homepage: http://loganalyzer.adiscon.com/ )


Abstract:
=========
An independent vulnerability laboratory researcher discovered a cross site scripting vulnerability in the log analyzer v3.6.0 web application.


Report-Timeline:
================
2012-12-20:    Public or Non-Public Disclosure


Status:
========
Published


Exploitation-Technique:
=======================
Remote


Severity:
=========
Low


Details:
========
A client side cross-site scripting vulnerability is detected in the LogAnalyzer 3.6.0 web application.
The vulnerability allows an remote attacker with high required user interaction to force client side xss requests.

The vulnerability is located in the asktheoracle.php file with the bound vulnerable oracle_query parameter request.
An attackers can force client side requests to execute arbitrary script code by using the oracle_query parameter.

Successful exploitation of the vulnerability results in client side execution of inject script, client side phishing,
client side module context manipulation and evil unautorized external redirects.

Vulnerable File(s):
                [+] asktheoracle.php

Vulnerable Parameter(s):
                [+] oracle_query


Proof of Concept:
=================
The client side cross site scripting vulnerability can be exploited by remote attackers with medium or high required user interaction
and without privileged application user account.

http://192.168.1.10:8080/loganalyzer-3.6.0/asktheoracle.php?type=searchstr&oracle_query=[CLIENT SIDE SCRIPT CODE!]

Note: The 'oracle_query' parameter didn't sanitize properly for asktheoracle.php page.


Solution:
=========
Upgrade to the latest version of Log Analyzer 3.6.1


Risk:
=====
The security risk of the client side cross site scripting web vulnerability is estimated as low(+)


Credits:
========
Mohd Izhar Ali - [http://johncrackernet.blogspot.com]


Disclaimer:
===========
The information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties,
either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business
profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases
or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com      - www.vuln-lab.com                  - www.vulnerability-lab.com/register
Contact:    admin@vulnerability-lab.com     - support@vulnerability-lab.com           - research@vulnerability-lab.com
Section:    video.vulnerability-lab.com     - forum.vulnerability-lab.com               - news.vulnerability-lab.com
Social:        twitter.com/#!/vuln_lab         - facebook.com/VulnerabilityLab           - youtube.com/user/vulnerability0lab
Feeds:        vulnerability-lab.com/rss/rss.php    - vulnerability-lab.com/rss/rss_upcoming.php  - vulnerability-lab.com/rss/rss_news.php

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory.
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed),
modify, use or edit our material contact (admin@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission.

                          Copyright © 2012 | Vulnerability Laboratory

Loganalyzer Cross Site Scripting Vulnerability in oracle_query paramater

Loganalyzer Cross Site Scripting Vulnerability in oracle_query paramater
A cross-site scripting vulnerability in the oracle_query parameter of the asktheoracle.php page was brought to our attention by Mohd Izhar Bin Ali. We thank then for giving us the chance to fix this issue before releasing information into the public. More details about the vulnerabilities can be found in this security advisory.

Affected Stable Versions:
Stable branch up to v3.6.0 (inclusive)

Fix:
Update to 3.6.1 or higher (if available)

Cross Site Scripting
Short Description:
A cross-site scripting vulnerability existed in the asktheoracle.php page. An attacker could use it to execute arbitrary HTML and Script code by using the oracle_query parameter.

Potential Impact:
An attacker could use prepared links to include and run scripts within the context of LogAnalyzer on the users browser.

Credits:
We want to thank Mohd Izhar Bin Ali for identifying these issues and working with us in resolving it. More details can be found in their advisory.

Wednesday, December 19, 2012

Kiwi Syslog Web Access 1.4.4 SQL Injection & Blind SQL Injection

Product: Kiwi Syslog Web Access
Version: 1.4.4
Vendor: http://www.kiwisyslog.com/kiwi-syslog-server-overview/
Vulnerability type: SQL Injection and Blind SQL Injection
Risk level: High
Vendor notification: 2012-12-18
Tested on: Windows 2003
Author: Mohd Izhar Ali

Kiwi Syslog Web Access version 1.4.4 suffers from remote SQL injection and blind SQL injection vulnerabilities.

You can download here:
http://packetstormsecurity.org/files/118945/Kiwi-Syslog-Web-Access-1.4.4-SQL-Injection.html

Tuesday, September 25, 2012

How to find latest IE vulnerability (CVE-2012-4969) with Nexpose


As you probably know, Microsoft released advisory 2757760 (Microsoft Security Advisory (2757760): Vulnerability in Internet Explorer Could Allow Remote Code Execution) which describes a Remote Code Execution vulnerability in Internet Explorer 7, 8, and 9. This was assigned to CVE-2012-4969 and Microsoft released a Security Update patch on September 21st, 2012 (Microsoft Security Bulletin MS12-063 - Critical : Cumulative Security Update for Internet Explorer (2744842)) to address this vulnerability.

Check out this blog about the 0-day exploit released by the Metasploit team on September 17th, 2012. As of Nexpose 5.4.5, released on September 22nd, 2012, you can also now find and remediate any assets that are vulnerable. Here's how:

To continue reading; please click here:

phpMyAdmin Compromised Source Package Backdoor Security Issue

A security issue has been reported in phpMyAdmin, which can be exploited by malicious people to compromise a vulnerable system. The security issue is caused due to the distribution of a compromised phpMyAdmin source code package containing a backdoor, which can be exploited to e.g. execute arbitrary PHP code.

Secunia ID
Release Date
25 Sep 2012
Criticality
Solution Status
Vendor Patch
Software
phpMyAdmin 3.x
Where
Impact
System access
This covers vulnerabilities where malicious people are able to gain system access and execute arbitrary code with the privileges of a local user.
Description
A security issue has been reported in phpMyAdmin, which can be exploited by malicious people to compromise a vulnerable system.
The security issue is caused due to the distribution of a compromised phpMyAdmin source code package containing a backdoor, which can be exploited to e.g. execute arbitrary PHP code.
The compromised source file was distributed via the "cdnetworks-kr-1" SourceForge mirror with the phpMyAdmin-3.5.2.2-all-languages.zip download.
Solution
Download and reinstall phpMyAdmin.
Reported by
The vendor credits Tencent Security Response Center.
Original Advisory

Saturday, February 04, 2012

FBI Arrests Suspected LulzSec and Anonymous Hackers

Search warrants were also being executed in New Jersey, Minnesota and Montana. The FBI  arrested two alleged members of the hacking collectives LulzSec and Anonymous on Thursday morning in San Francisco and Phoenix, According to Fox news. The suspected hacker arrested in California is homeless and alleged to have been involved in the hacking of Santa Cruz County government websites.

The person arrested in Arizona is a student at a technical university and allegedly participated in the widely publicized hack against Sony. Both groups have been targeted by the FBI and international law enforcement agencies in recent months.

Meanwhile, the FBI arrested an alleged Anonymous member in San Francisco. The man, who is reported to be homeless, is said to have been involved in internet attacks against Santa Cruz County government websites.Just because a man is homeless, of course, doesn't mean that he can't get an internet connection. Coffee houses, cafes, libraries, etc can all offer cheap or free internet access - and because the computer being used can be a shared device, it may be harder to identify who might have been responsible for an attack compared to a PC at a home.

The arrests shouldn't surprise anyone. They made two errors:
Mistake #1: They brough too much attention to themselves.
It is said that John Gotti, the mafia boss, brought so much attention to himself that he became a natural, high profile target for law enforcement. As Amichai Shulman, our CTO, stated before, the Lulzsec, the hackers "were extremely unfocused in their goal and gained attention mainly due to the relative intensity of their activity and lack of other good media topics." They brought too much attention to themselves and you could expect law enforcement to find them. If you look at hacking historically, over the past 20 years many of the high-profile attacks or those that involve serious losses to governments or commercial companies have ended up with law enforcement finding the perpetrators eventually, such as Albert Gonzalez.

Mistake #2: They didn't cover up their tracks.
Let's review some of the Lulzsec chat logs from a few months ago. One snippet, in reference to discussions Lulzsec was having with the media, shows how the hackers themselves admit they gave away too much informaiton:
Topiary - Sabu and I got a bit carried away and gave LulzSec away a bit
As Imperva's Tal Be'ery said in this USA Today article, "When you're running this kind of operation for a long time, especially with not very concrete plans, you're bound to make mistakes." The mistakes Lulzsec and Anonymous made during their hacking spree left an electronic trail with enough foot prints to product today's arrests.