This exploit is a buffer overflow vulnerability in the Uploader!23151EXE application. It allows an attacker to execute arbitrary code by overflowing a buffer with malicious data. The exploit is triggered when the application is passed a specially crafted file, uploadpref.dat, which contains a malicious payload. The payload contains a shellcode that executes calc.exe when the application is run.
SpagoBI contains a flaw that may allow a remote attacker to execute arbitrary code. This flaw exists because the application does not restrict uploading for specific file types from Worksheet designer function. This may allow a remote attacker to upload arbitrary files (e.g. .html for XSS) that would execute arbitrary script code in a user's browser within the trust relationship between their browser and the server or more easily conduct more serious attacks.
SpagoBI contains a flaw that allows persistent script insertion. This may allow a remote attacker to inject HTML code including forms that load on a remote site, which can allow the attacker to conduct a phishing attack on a user and capture their credentials.
SpagoBI contains a flaw that allows persistent cross-site scripting (XSS) attacks. This flaw exists because the application does not validate certain unspecified input before returning it to the user. This may allow an attacker to create a specially crafted request that would execute arbitrary script code in a user's browser within the trust relationship between their browser and the server.
couponPHP is vulnerable to multiple Stored XSS and SQL Injection issues. Input passed via the parameters 'iDisplayLength' and 'iDisplayStart' in 'comments_paginate.php' and 'stores_paginate.php' scripts are not properly sanitised before being returned to the user or used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. The parameter 'sEcho' in 'comments_paginate.php' and 'stores_paginate.php' and the parameters 'affiliate_url', 'description', 'domain', 'seo[description]', 'seo[heading]', 'seo[title]', 'seo[keywords]', 'setting[logo]', 'setting[perpage]' and 'setting[sitename]' in '/admin/index.php' script are vulnerable to stored XSS issues where the attacker can execute arbitrary HTML and script code in a user's browser session in context of an affected site.
A remote, unauthenticated attacker could exploit this issue in combination with other found issues, to extract the database credentials and instance name. The target URL is http://target.com:8080/demantra/ServerDetailsServlet?UAK= and the UAK key is calculated statically. A simple extractor can be created to exploit this vulnerability unauthenticated.
An attacker could exploit this flaw to get active HTML or script code executed in an authenticated user’s browser. Cross-site Scripting may be used to perform attacks such as session hijacking by invoking the user’s browser to send information stored in their cookies (such as a session identification token) to an arbitrary location controlled by the attacker. Furnished with this information the attacker could immediately access the site, masquerading as the authenticated user who viewed the page containing the malicious code. The attacker would then be able to perform actions as the authorised user, subject to their role, which could include viewing sensitive data, modifying profile information and making transactions. This vulnerability could also be leveraged in a “phishing” attack, whereby the attacker adds additional HTML code to create a false login page within the vulnerable page, which posts the data to a server controlled by the attacker. The attacker could then redirect the user back to the original server, thus giving the illusion that the login was secure and genuine. This could also be achieved by redirecting the user to a false login page on the attacker’s server rather than adding the code to a page that already exists. This is critical, because if the attacker could host a “phishing” website in a domain with a valid SSL certificate, there would be no way for a user to spot the attack. A variation of the “phishing” attack described above would be to inject code to completely rewrite the genuine page, defacing the site and possibly having a detrimental impact on the reputation of the company. Finally, an attacker could use Cross-site Scripting to exploit vulnerabilities within web browsers. The outcome of such an attack would depend on the exploits used, but in a worst case scenario the attacker could gain full control of a user’s computer.
An attacker with access to the vulnerable pages could manipulate the queries being sent to the database, potentially enabling them to extract sensitive information, including (but not limited to) authentication credentials and personal details. Such information could be sold by the attacker to other malicious individuals, used in other attacks (as the same password is often used across systems) or released publicly to damage the organisation’s reputation. The attacker could also modify content within the application, potentially adding malicious code to the application, which could then be used to deliver malware or exploit issues within client browsers. In this particular instance, exploitation was more difficult as the results of the attack had to inferred based on the pages returned, often referred to as “blind” SQL Injection.
A file inclusion vulnerability occurs when a file from the target system is injected into a page on the attacked server page. Impact can differ based on the exploitation and the read permission of the web server user. Depending on these factors an attacker might carry out one or more of the following attacks: Harvest useful information from the web.xml configuration file, Download the whole web application source code like the vulnerable page itself.
SpagoBI contains a flaw that leads to unauthorized privileges being gained. The issue is triggered when the servlet (action): AdapterHTTP?ACTION_NAME=MANAGE_USER_ACTION is executed with specifically crafted input, and may allow a remote attacker to gain Administrator role privileges. An attacker (a SpagoBI malicious Business User with RSM role ) can invoke via URL the servlet (action): AdapterHTTP?ACTION_NAME=MANAGE_USER_ACTION to gain SpagoBI Administrator privilege.
Services By CQR