Test Ability to forge requests (OTG-BUSLOGIC-002) - Revision history

Andrew Muller at 13:04, 8 August 2014

2014-08-08T13:04:30Z

Jane O'Connor: Added Andrew's changes.

2014-08-01T21:17:52Z

Added Andrew's changes.

Jane O'Connor at 11:18, 19 May 2014

2014-05-19T11:18:44Z

Jane O'Connor: Final edit

2014-05-19T11:18:18Z

Final edit

David Fern at 03:27, 17 December 2013

2013-12-17T03:27:57Z

David Fern at 03:21, 17 December 2013

2013-12-17T03:21:37Z

David Fern at 03:21, 17 December 2013

2013-12-17T03:21:05Z

David Fern at 14:12, 16 December 2013

2013-12-16T14:12:51Z

David Fern at 14:12, 16 December 2013

2013-12-16T14:12:05Z

David Fern at 13:29, 16 December 2013

2013-12-16T13:29:06Z

@@ Line 53: / Line 53: @@
 == Related Test Cases ==
-.7.5 Testing for Cross Site Request Forgery (CSRF) (OTG-SESS-005)
+[[Testing for Exposed Session Variables  (OTG-SESS-004)| Testing for Exposed Session Variables (OTG-SESS-004)]]
-.4.4 Testing for Account Enumeration and Guessable User Account (OTG-IDENT-004)
+[[Testing for CSRF  (OTG-SESS-005)| Testing for Cross Site Request Forgery (CSRF) (OTG-SESS-005)]]

@@ Line 1: / Line 1: @@
-== Brief Description ==
+== Summary ==
 Forging requests is a method that attackers use to circumvent the front end GUI application to directly submit information for back end processing. The goal of the attacker is to send HTTP POST/GET requests through an intercepting proxy with data values that is not supported, guarded against or expected by the applications business logic. Some examples of forged requests include exploiting guessable or predictable parameters or expose “hidden” features and functionality such as enabling debugging or presenting special screens or windows that are very useful during development but may leak information or bypass the business logic.
@@ Line 6: / Line 6: @@
 Vulnerabilities related to the ability to forge requests is unique to each application and different from business logic data validation in that it s focus is on breaking the business logic workflow.
 Applications should have logic checks in place to prevent the system from accepting  forged requests that may allow attackers the opportunity to exploit the business logic, process, or flow of the application. Request forgery is nothing new; the attacker uses an intercepting proxy to send HTTP POST/GET requests to the application. Through request forgeries attackers may be able to circumvent the business logic or process by finding, predicting and manipulating parameters to make the application think a process or task has or has not taken place.
@@ Line 30: / Line 28: @@
-== Testing Method ==
+== How to Test==
 Generic Testing Method
@@ Line 53: / Line 51: @@
-== Test Tools ==
+== Related Test Cases ==
-''OWASP Zed Attack Proxy (ZAP)'' - https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project
+.7.5 Testing for Cross Site Request Forgery (CSRF) (OTG-SESS-005)
-ZAP is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.
+.4.4 Testing for Account Enumeration and Guessable User Account (OTG-IDENT-004)
-== Related Test Cases ==
+== Tools ==
-.7.5 Testing for Cross Site Request Forgery (CSRF) (OTG-SESS-005)
+''OWASP Zed Attack Proxy (ZAP)'' - https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project
-.4.4 Testing for Account Enumeration and Guessable User Account (OTG-IDENT-004)
+ZAP is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.

← Older revision		Revision as of 11:18, 19 May 2014
Line 10:		Line 10:

	Applications should have logic checks in place to prevent the system from accepting forged requests that may allow attackers the opportunity to exploit the business logic, process, or flow of the application. Request forgery is nothing new; the attacker uses an intercepting proxy to send HTTP POST/GET requests to the application. Through request forgeries attackers may be able to circumvent the business logic or process by finding, predicting and manipulating parameters to make the application think a process or task has or has not taken place.		Applications should have logic checks in place to prevent the system from accepting forged requests that may allow attackers the opportunity to exploit the business logic, process, or flow of the application. Request forgery is nothing new; the attacker uses an intercepting proxy to send HTTP POST/GET requests to the application. Through request forgeries attackers may be able to circumvent the business logic or process by finding, predicting and manipulating parameters to make the application think a process or task has or has not taken place.
		+

	Also, forged requests may allow subvention of programmatic or business logic flow by invoking “hidden” features or functionality such as debugging initially used by developers and testers sometimes referred to as an ”Easter egg”. “An Easter egg is an intentional inside joke, hidden message, or feature in a work such as a computer program, movie, book, or crossword. According to game designer Warren Robinett, the term was coined at Atari by personnel who were alerted to the presence of a secret message which had been hidden by Robinett in his already widely distributed game, Adventure. The name has been said to evoke the idea of a traditional Easter egg hunt.” http://en.wikipedia.org/wiki/Easter_egg_(media)		Also, forged requests may allow subvention of programmatic or business logic flow by invoking “hidden” features or functionality such as debugging initially used by developers and testers sometimes referred to as an ”Easter egg”. “An Easter egg is an intentional inside joke, hidden message, or feature in a work such as a computer program, movie, book, or crossword. According to game designer Warren Robinett, the term was coined at Atari by personnel who were alerted to the presence of a secret message which had been hidden by Robinett in his already widely distributed game, Adventure. The name has been said to evoke the idea of a traditional Easter egg hunt.” http://en.wikipedia.org/wiki/Easter_egg_(media)

@@ Line 1: / Line 1: @@
 == Brief Description ==
-Forging requests is a method that attackers use to circumvent the front end GUI application to directly submit information for backend processing. The goal of the attacker is to send HTTP POST/GET requests through an intercepting proxy with data values that is not supported, guarded against or expected by the applications business logic. Some examples of forged requests include exploiting guessable or predictable parameters or expose “hidden” features and functionality such as enabling debugging or presenting special screens or windows that are very useful during development but may leak information or bypass the business logic.
+Forging requests is a method that attackers use to circumvent the front end GUI application to directly submit information for back end processing. The goal of the attacker is to send HTTP POST/GET requests through an intercepting proxy with data values that is not supported, guarded against or expected by the applications business logic. Some examples of forged requests include exploiting guessable or predictable parameters or expose “hidden” features and functionality such as enabling debugging or presenting special screens or windows that are very useful during development but may leak information or bypass the business logic.
 Vulnerabilities related to the ability to forge requests is unique to each application and different from business logic data validation in that it s focus is on breaking the business logic workflow.
 == Issue ==
-Applications should have logic checks in place to prevent the system from accepting  forged requests that may allow attackers the opportunity to exploit the business logic, process, or flow of the application.
+Applications should have logic checks in place to prevent the system from accepting  forged requests that may allow attackers the opportunity to exploit the business logic, process, or flow of the application. Request forgery is nothing new; the attacker uses an intercepting proxy to send HTTP POST/GET requests to the application. Through request forgeries attackers may be able to circumvent the business logic or process by finding, predicting and manipulating parameters to make the application think a process or task has or has not taken place.
-Also, forged requests may allow subvention of programmatic or business logic flow by invoking “hidden” features or functionality such as debugging initially used by developers and testers sometimes referred to as an ”Easter egg”.
+Also, forged requests may allow subvention of programmatic or business logic flow by invoking “hidden” features or functionality such as debugging initially used by developers and testers sometimes referred to as an ”Easter egg”. “An Easter egg is an intentional inside joke, hidden message, or feature in a work such as a computer program, movie, book, or crossword. According to game designer Warren Robinett, the term was coined at Atari by personnel who were alerted to the presence of a secret message which had been hidden by Robinett in his already widely distributed game, Adventure. The name has been said to evoke the idea of a traditional Easter egg hunt.” http://en.wikipedia.org/wiki/Easter_egg_(media)
 == Examples ==
 Example 1
-Suppose an e-commerce theatre site allows users to select their ticket, apply a onetime 10% Senior discount on the entire sale, view the subtotal and tender the sale. If an attacker is able to see through a proxy that the application has a hidden field (of 1 or 0) used by the business logic to determine if a discount has been taken or not. The attacker is then able to submit the 1 or “no discount has been taken” value multiple times to take advantage of the same discount multiple times.
+Suppose an e-commerce theater site allows users to select their ticket, apply a onetime 10% Senior discount on the entire sale, view the subtotal and tender the sale. If an attacker is able to see through a proxy that the application has a hidden field (of 1 or 0) used by the business logic to determine if a discount has been taken or not. The attacker is then able to submit the 1 or “no discount has been taken” value multiple times to take advantage of the same discount multiple times.
@@ Line 28: / Line 24: @@
 Suppose an online video game pays out tokens for points scored for finding pirates treasure and pirates and for each level completed. These tokens can later be that can later be exchanged for prizes. Additionally each level's points have a multiplier value equal to the level. If an attacker was able to see through a proxy that the application has a hidden field used during development and testing to quickly get to the highest levels of the game they could quickly get to the highest levels and accumulate unearned points quickly.
 Also, if an attacker was able to see through a proxy that the application has a hidden field used during development and testing to enabled a log that indicated where other online players, or hidden treasure were in relation to the attacker, they would then be able to quickly go to these locations and score points.
 == Testing Method ==
 Generic Testing Method
@@ Line 53: / Line 50: @@
 •	If any are found try to guess and change these values to get a different application  response or behavior.
 == Test Tools ==
@@ Line 59: / Line 57: @@
 ZAP is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.
 == Related Test Cases ==
@@ Line 67: / Line 66: @@
 .4.4 Testing for Account Enumeration and Guessable User Account (OTG-IDENT-004)
 == References ==
@@ Line 79: / Line 79: @@
 Top 10 Software Easter Eggs - http://lifehacker.com/371083/top-10-software-easter-eggs
 == Remediation ==
 The application must be smart enough and designed with business logic that will prevent attackers from predicting and manipulating parameters to subvert programmatic or business logic flow, or exploiting hidden/undocumented functionality such as debugging.

@@ Line 18: / Line 18: @@
 == Examples ==
 Example 1
 Suppose an e-commerce theatre site allows users to select their ticket, apply a onetime 10% Senior discount on the entire sale, view the subtotal and tender the sale. If an attacker is able to see through a proxy that the application has a hidden field (of 1 or 0) used by the business logic to determine if a discount has been taken or not. The attacker is then able to submit the 1 or “no discount has been taken” value multiple times to take advantage of the same discount multiple times.
 Example 2
@@ Line 30: / Line 32: @@
 == Testing Method ==
 Generic Testing Method

← Older revision		Revision as of 03:21, 17 December 2013
Line 43:		Line 43:

	• If it is found that some value is guessable this value may be changed and one may gain unexpected visibility.		• If it is found that some value is guessable this value may be changed and one may gain unexpected visibility.
		+

	Specific Testing Method 2		Specific Testing Method 2

@@ Line 2: / Line 2: @@
 Forging requests is a method that attackers use to circumvent the front end GUI application to directly submit information for backend processing. The goal of the attacker is to send HTTP POST/GET requests through an intercepting proxy with data values that is not supported, guarded against or expected by the applications business logic. Some examples of forged requests include exploiting guessable or predictable parameters or expose “hidden” features and functionality such as enabling debugging or presenting special screens or windows that are very useful during development but may leak information or bypass the business logic.
 == Issue ==
@@ Line 15: / Line 17: @@
 “An Easter egg is an intentional inside joke, hidden message, or feature in a work such as a computer program, movie, book, or crossword. According to game designer Warren Robinett, the term was coined at Atari by personnel who were alerted to the presence of a secret message which had been hidden by Robinett in his already widely distributed game, Adventure. The name has been said to evoke the idea of a traditional Easter egg hunt.” http://en.wikipedia.org/wiki/Easter_egg_(media)
-== Example ==
+== Examples ==
-== Example 1 ==
+Example 1
 Suppose an e-commerce theatre site allows users to select their ticket, apply a onetime 10% Senior discount on the entire sale, view the subtotal and tender the sale. If an attacker is able to see through a proxy that the application has a hidden field (of 1 or 0) used by the business logic to determine if a discount has been taken or not. The attacker is then able to submit the 1 or “no discount has been taken” value multiple times to take advantage of the same discount multiple times.
-== Example 2 ==
+Example 2
-Suppose an online video game pays out tokens for points scored for finding pirates treasure and pirates and for each level completed. These tokens can later be  that can later be exchanged for prizes,. aAdditionally each level's points have a multiplier value equal to the level. If an attacker was able to see through a proxy that the application has a hidden field used during development and testing to quickly get to the highest levels of the game they could quickly get to the highest levels and accumulate unearned points quickly.
+Suppose an online video game pays out tokens for points scored for finding pirates treasure and pirates and for each level completed. These tokens can later be that can later be exchanged for prizes. Additionally each level's points have a multiplier value equal to the level. If an attacker was able to see through a proxy that the application has a hidden field used during development and testing to quickly get to the highest levels of the game they could quickly get to the highest levels and accumulate unearned points quickly.
 Also, if an attacker was able to see through a proxy that the application has a hidden field used during development and testing to enabled a log that indicated where other online players, or hidden treasure were in relation to the attacker, they would then be able to quickly go to these locations and score points.
@@ Line 29: / Line 31: @@
 == Testing Method ==
-== Generic Testing Method ==
+Generic Testing Method
-== Specific Testing Method 1 ==
+Specific Testing Method 1
 •	Using an intercepting proxy observe the HTTP POST/GET looking for some indication that values are incrementing at a regular interval or are easily guessable.
@@ Line 39: / Line 44: @@
 •	If it is found that some value is guessable this value may be changed and one may gain unexpected visibility.
-== Specific Testing Method 2 ==
+Specific Testing Method 2
 •	Using an intercepting proxy observe the HTTP POST/GET looking for some indication of hidden features such as debug that can be switched on or activated.