Difference between revisions of "Failure to encrypt data"

From OWASP
Jump to: navigation, search
m (Added cross references for related attacks and risks)
 
(7 intermediate revisions by one user not shown)
Line 1: Line 1:
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
 +
{{Template:Vulnerability}}
  
==Overview==
+
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
The failure to encrypt data passes up the guarantees of confidentiality, integrity, and accountability that properly implemented encryption conveys.
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
  
==Consequences ==
+
==Description==
  
* Confidentiality: Properly encrypted data channels ensure data confidentiality.
+
The failure to encrypt data passes up the guarantees of confidentiality, integrity, and accountability that properly implemented encryption conveys.  
  
* Integrity: Properly encrypted data channels ensure data integrity.
+
'''Consequences'''
  
* Accountability: Properly encrypted data channels ensure accountability.
+
* Confidentiality: Properly encrypted data channels ensure data confidentiality.
 +
* Integrity: Properly encrypted data channels ensure data integrity.
 +
* Accountability: Properly encrypted data channels ensure accountability.
  
==Exposure period ==
+
'''Exposure period'''
  
* Requirements specification: Encryption should be a requirement of systems that transmit data.
+
* Requirements specification: Encryption should be a requirement of systems that transmit data.
 +
* Design: Encryption should be designed into the system at the architectural and design phases
  
* Design: Encryption should be designed into the system at the architectural and design phases
+
'''Platform'''
  
==Platform ==
+
* Languages: Any
 +
* Operating platform: Any
  
* Languages: Any
+
'''Required resources'''
 
+
* Operating platform: Any
+
 
+
==Required resources ==
+
  
 
Any
 
Any
  
==Severity ==
+
'''Severity'''
  
 
High
 
High
  
==Likelihood  of exploit ==
+
'''Likelihood  of exploit'''
  
 
Very High
 
Very High
 
==Avoidance and mitigation ==
 
 
* Requirements specification: require that encryption be integrated into the system.
 
 
* Design: Ensure that encryption is properly integrated into the system design, not simply as a drop-in replacement for sockets.
 
 
==Discussion ==
 
  
 
Omitting the use of encryption in any program which transfers data over a network of any kind should be considered on par with delivering the data sent to each user on the local networks of both the sender and receiver.  
 
Omitting the use of encryption in any program which transfers data over a network of any kind should be considered on par with delivering the data sent to each user on the local networks of both the sender and receiver.  
Line 49: Line 42:
 
Worse, this omission allows for the injection of data into a stream of communication between two parties - with no means for the victims to separate valid data from invalid.
 
Worse, this omission allows for the injection of data into a stream of communication between two parties - with no means for the victims to separate valid data from invalid.
  
In this day of widespread network attacks and password collection sniffers, it is an unnecessary risk to omit encryption from the design of any system which might benefit from it.  
+
In this day of widespread network attacks and password collection sniffers, it is an unnecessary risk to omit encryption from the design of any system which might benefit from it.
  
==Examples ==
+
==Risk Factors==
 +
 
 +
* [[Man-in-the-middle_attack|Man in the middle attack]]
 +
 
 +
==Examples==
  
 
In C:
 
In C:
Line 84: Line 81:
 
</pre>
 
</pre>
  
==Related problems ==
 
  
Not available.
+
==Related [[Attacks]]==
  
 +
* [[Argument_Injection_or_Modification|Argument Injection or Modification]]
 +
* [[Network_Eavesdropping|Network Eavesdropping]]
 +
* [[Repudiation_Attack|Repudiation Attack]]
  
[[Category:Vulnerability]]
 
  
[[Category:Protocol Errors]]
+
==Related [[Vulnerabilities]]==
  
 +
* [[Vulnerability 1]]
 +
* [[Vulnerabiltiy 2]]
 +
 +
 +
==Related [[Controls]]==
 +
 +
* Requirements specification: require that encryption be integrated into the system.
 +
* Design: Ensure that encryption is properly integrated into the system design, not simply as a drop-in replacement for sockets.
 +
 +
 +
==Related [[Technical Impacts]]==
 +
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
 +
 +
 +
==References==
 +
TBD
 +
 +
 +
__NOTOC__
 +
 +
 +
[[Category:OWASP ASDR Project]]
 +
[[Category:Vulnerability]]
 +
[[Category:Protocol Errors]]
 
[[Category:OWASP_CLASP_Project]]
 
[[Category:OWASP_CLASP_Project]]
 +
[[Category: Cryptographic  Vulnerability]]

Latest revision as of 07:40, 10 August 2012

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


Last revision (mm/dd/yy): 08/10/2012

Vulnerabilities Table of Contents

Description

The failure to encrypt data passes up the guarantees of confidentiality, integrity, and accountability that properly implemented encryption conveys.

Consequences

  • Confidentiality: Properly encrypted data channels ensure data confidentiality.
  • Integrity: Properly encrypted data channels ensure data integrity.
  • Accountability: Properly encrypted data channels ensure accountability.

Exposure period

  • Requirements specification: Encryption should be a requirement of systems that transmit data.
  • Design: Encryption should be designed into the system at the architectural and design phases

Platform

  • Languages: Any
  • Operating platform: Any

Required resources

Any

Severity

High

Likelihood of exploit

Very High

Omitting the use of encryption in any program which transfers data over a network of any kind should be considered on par with delivering the data sent to each user on the local networks of both the sender and receiver.

Worse, this omission allows for the injection of data into a stream of communication between two parties - with no means for the victims to separate valid data from invalid.

In this day of widespread network attacks and password collection sniffers, it is an unnecessary risk to omit encryption from the design of any system which might benefit from it.

Risk Factors

Examples

In C:

server.sin_family = AF_INET;
hp = gethostbyname(argv[1]);
if (hp==NULL) error("Unknown host");
memcpy( (char *)&server.sin_addr,(char *)hp->h_addr,hp->h_length);
if (argc < 3) port = 80;
else port = (unsigned short)atoi(argv[3]);
server.sin_port = htons(port); 
	if (connect(sock, (struct sockaddr *)&server, sizeof server) < 0)
         error("Connecting");
...

  while ((n=read(sock,buffer,BUFSIZE-1))!=-1){
          write(dfd,password_buffer,n);
.
.
.

In Java:

try {
  URL u = new URL("http://www.importantsecretsite.org/");
  HttpURLConnection hu = (HttpURLConnection) u.openConnection();
  hu.setRequestMethod("PUT");
  hu.connect();
  OutputStream os = hu.getOutputStream();
  hu.disconnect();
}
catch (IOException e) { //...


Related Attacks


Related Vulnerabilities


Related Controls

  • Requirements specification: require that encryption be integrated into the system.
  • Design: Ensure that encryption is properly integrated into the system design, not simply as a drop-in replacement for sockets.


Related Technical Impacts


References

TBD