Difference between revisions of "Insecure Transport"

From OWASP
Jump to: navigation, search
(Related Attacks)
 
(3 intermediate revisions by one user not shown)
Line 1: Line 1:
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
 
{{Template:Fortify}}
 
{{Template:Fortify}}
 
__TOC__
 
 
[[ASDR Table of Contents]]
 
  
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 
+
  
 
==Description==
 
==Description==
 
 
The application configuration should ensure that SSL is used for all access controlled pages.
 
The application configuration should ensure that SSL is used for all access controlled pages.
  
If an application uses SSL to guarantee confidential communication with client browsers, the application configuration should make it impossible to view any access controlled page without SSL. However, it is not a uncommon problem that the configuration of the application fails to enforce the use of SSL on pages that contain sensitive data.  
+
If an application uses SSL to guarantee confidential communication with client browsers, the application configuration should make it impossible to view any access controlled page without SSL. However, it is not an uncommon problem that the configuration of the application fails to enforce the use of SSL on pages that contain sensitive data.  
  
 
There are three common ways for SSL to be bypassed:
 
There are three common ways for SSL to be bypassed:
  
* A user manually enters URL and types "HTTP" rather than "HTTPS"  
+
* A user manually enters the URL and types "HTTP" rather than "HTTPS".
* Attackers intentionally send a user to an insecure URL  
+
* Attackers intentionally send a user to an insecure URL.
* A programmer erroneously creates a relative link to a page in the application, failing to switch from HTTP to HTTPS. (This is particularly easy to do when the link moves between public and secured areas on a web site.)  
+
* A programmer erroneously creates a relative link to a page in the application, failing to switch from HTTP to HTTPS. (This is particularly easy to do when the link moves between public and secured areas on a web site.)
 
+
  
 
==Risk Factors==
 
==Risk Factors==
Line 36: Line 29:
 
==Related [[Attacks]]==
 
==Related [[Attacks]]==
  
* Attackers that are trying to steal login credentials, session ids or other sensitive information
+
* Attackers that are trying to steal login credentials, session IDs or other sensitive information
 
* Bypassing SSL by entering HTTP instead of HTTPS
 
* Bypassing SSL by entering HTTP instead of HTTPS
* Sending insecure URLs of protected pages to the victim (e.g. login page) to trick the victim into accessing the privileged pages via HTTP  
+
* Sending insecure URLs of protected pages to the victim (e.g. login page) to trick the victim into accessing the privileged pages via HTTP
 
+
 
+
  
 
==Related [[Vulnerabilities]]==
 
==Related [[Vulnerabilities]]==

Latest revision as of 06:26, 26 February 2009

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.


This article includes content generously donated to OWASP by Fortify.JPG.

Last revision (mm/dd/yy): 02/26/2009

Vulnerabilities Table of Contents

Description

The application configuration should ensure that SSL is used for all access controlled pages.

If an application uses SSL to guarantee confidential communication with client browsers, the application configuration should make it impossible to view any access controlled page without SSL. However, it is not an uncommon problem that the configuration of the application fails to enforce the use of SSL on pages that contain sensitive data.

There are three common ways for SSL to be bypassed:

  • A user manually enters the URL and types "HTTP" rather than "HTTPS".
  • Attackers intentionally send a user to an insecure URL.
  • A programmer erroneously creates a relative link to a page in the application, failing to switch from HTTP to HTTPS. (This is particularly easy to do when the link moves between public and secured areas on a web site.)

Risk Factors

TBD

Examples

  • Login pages are not SSL protected
  • A publicly accessible page contains a relative link to a protected page which forgets to switch to SSL.


Related Attacks

  • Attackers that are trying to steal login credentials, session IDs or other sensitive information
  • Bypassing SSL by entering HTTP instead of HTTPS
  • Sending insecure URLs of protected pages to the victim (e.g. login page) to trick the victim into accessing the privileged pages via HTTP

Related Vulnerabilities


Related Controls


Related Technical Impacts


References

TBD