Daar komen een hoop fouten in voor. Alle low maar 6 HGH risk. Nou is die klant natuurlijk nerveus en toch gebruik ik laatste Joomla 2.5.19 versie en laatste versie van Hikashop business. Hie komen ze dan aan zo'n resultaat? Ik heb idee dat het een beetje onzin is. Komen ze aan met een pdf report van 142!!! pagina's.
Iemand enig idee wat ik ermee aanmoet? Voorbeeldje van een HIGH risk :
Code: Select all
150001 Reflected Cross-Site Scripting (XSS) Vulnerabilities New
URL: https://www.domeinnaam.nl/en/?
option=com_hikashop&ctrl=checkout&task=state&tmpl=component&field_type=address&field_id=data_address_address_state&field_namekey=%22%20onEvent
%3DX3066908532Y7Z%20&namekey=country_Algeria_3
Finding # 164840669 First Time Detected 27 Apr 2014 09:49 GMT+0200
Group Cross-Site Scripting Last Time Detected 27 Apr 2014 09:49 GMT+0200
CWE CWE-79 Last Time Tested 27 Apr 2014 09:49 GMT+0200
OWASP A3 Cross-Site Scripting (XSS) Times Detected 1
WASC WASC-8 Cross-Site Scripting
CVSS Base 4.3 CVSS Temporal3.9
Details
Threat
XSS vulnerabilities occur when the Web application echoes user-supplied data in an HTML response sent to the Web browser. For example, a Web application
might include the user's name as part of a welcome message or display a home address when confirming a shipping destination. If the user-supplied data contain
characters that are interpreted as part of an HTML element instead of literal text, then an attacker can modify the HTML that is received by the victim's Web browser.
The XSS payload is echoed in HTML document returned by the request. An XSS payload may consist of HTML, JavaScript or other content that will be rendered by
the browser. In order to exploit this vulnerability, a malicious user would need to trick a victim into visiting the URL with the XSS payload.
Impact
XSS exploits pose a significant threat to a Web application, its users and user data. XSS exploits target the users of a Web application rather than the Web
application itself. An exploit can lead to theft of the user's credentials and personal or financial information. Complex exploits and attack scenarios are possible via
XSS because it enables an attacker to execute dynamic code. Consequently, any capability or feature available to the Web browser (for example HTML, JavaScript,
Flash and Java applets) can be used to as a part of a compromise.
Solution
Filter all data collected from the client including user-supplied content and browser content such as Referrer and User-Agent headers.
Any data collected from the client and displayed in a Web page should be HTML-encoded to ensure the content is rendered as text instead of an HTML element or
JavaScript.
Detection Information
Parameter It has been detected by exploiting the parameter field_namekey
The payloads section will display a list of tests that show how the param could have been exploited to collect the information
Authentication In order to detect this vulnerability, no authentication has been required.
Access Path Here is the path followed by the scanner to reach the exploitable URL:
http://www.domeinnaam.nl/
https://www.domeinnaam.nl/en/component/users/?view=login
https://www.domeinnaam.nl/en/new-customer
https://www.domeinnaam.nl/index.php?
option=com_hikashop&ctrl=checkout&task=state&tmpl=component&field_type=address&field_id=data_address_address_state&field_namekey=address_state&namekey=country_Algeria_3