Hi everyone,
Recently , my company had asked a third party to do a Web Application Vulnerability Assessment & Penetration Testing on my web application that I build using Alpha Anywhere version 4.4.4.The objective of this assessment is to detect potential vulnerabilities and weaknesses on my web application . After the assessment they will come out with findings that I need to fix before they can produce a full report of the assessment that can be send to certain organization at my country. I have a few finding that I need to consult as I dont really know how to fix it. The finding that they gave me are, i) File Path Manipulation Issues and ii) Cross Site Scripting Issues. This issues were categorized as high (The materialized of identified risk would result in significant impact and direct loss in Confidentiality, Integrity, and/or Availability toward organization asset. This usually require immediate attention for remediation.) and seriously in need to be fix / justify .
Below is some explanations about the issues.
1) File path manipulation vulnerabilities arise when user-controllable data is placed into a file or URL path that is used on the server to access local resources, which may be within or outside the web root. If vulnerable, an attacker can modify the file path to access different resources, which may contain sensitive information. Even where an attack is constrained within the web root, it is often possible to retrieve items that are normally protected from direct access, such as application configuration files, the source code for server-executable scripts, or files with extensions that the web server is not configured to serve directly.
2)Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request that, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application. The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes. Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site that causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method). The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality that it contains, and the other applications that belong to the same domain and organization. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain that can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organization that owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application and exploiting users' trust in the organization to capture credentials for other applications that it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Attached is the extra details for the finding.Hope that someone will help/guide me to fix this or find a workaround for this.Right now I`m still trying to figure out how to fix it by myself.
appendix assessment.doc
Recently , my company had asked a third party to do a Web Application Vulnerability Assessment & Penetration Testing on my web application that I build using Alpha Anywhere version 4.4.4.The objective of this assessment is to detect potential vulnerabilities and weaknesses on my web application . After the assessment they will come out with findings that I need to fix before they can produce a full report of the assessment that can be send to certain organization at my country. I have a few finding that I need to consult as I dont really know how to fix it. The finding that they gave me are, i) File Path Manipulation Issues and ii) Cross Site Scripting Issues. This issues were categorized as high (The materialized of identified risk would result in significant impact and direct loss in Confidentiality, Integrity, and/or Availability toward organization asset. This usually require immediate attention for remediation.) and seriously in need to be fix / justify .
Below is some explanations about the issues.
1) File path manipulation vulnerabilities arise when user-controllable data is placed into a file or URL path that is used on the server to access local resources, which may be within or outside the web root. If vulnerable, an attacker can modify the file path to access different resources, which may contain sensitive information. Even where an attack is constrained within the web root, it is often possible to retrieve items that are normally protected from direct access, such as application configuration files, the source code for server-executable scripts, or files with extensions that the web server is not configured to serve directly.
2)Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request that, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application. The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes. Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site that causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method). The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality that it contains, and the other applications that belong to the same domain and organization. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain that can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organization that owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application and exploiting users' trust in the organization to capture credentials for other applications that it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Attached is the extra details for the finding.Hope that someone will help/guide me to fix this or find a workaround for this.Right now I`m still trying to figure out how to fix it by myself.
appendix assessment.doc
Comment