Category:Sensitive Data Protection Vulnerability - Revision history

Forest Monsen: Undo revision 89209 by Frank Alexander (talk): Reverting direct link to an EXE file.

2012-04-04T18:50:44Z

Undo revision 89209 by Frank Alexander (talk): Reverting direct link to an EXE file.

Frank Alexander at 18:25, 13 September 2010

2010-09-13T18:25:22Z

Weilin Zhong at 20:16, 12 June 2006

2006-06-12T20:16:45Z

New page

This category is for tagging vulnerabilities that lead to insecure protection of sensitive data. The protection referred here includes confidentiality and integrity of data during its whole lifecycles, including storage and transmission.

Please note that this category is intended to be different from access control problems, although they both fail to protect data appropriately. Normally, the goal of access control is to grant data access to some users but not others. In this category, we are instead concerned about protection for sensitive data that are not intended to be revealed to or modified by any application users. Examples of this kind of sensitive data can be cryptographic keys, passwords, security tokens or any information that an application relies on for critical decisions.

Examples of this vulnerability can be:
* Information leakage results from insufficient memory clean-up
* Inappropriate protection of cryptographic keys (This should also be labeled with Category:Cryptography)
* Clear-text Passwords in configration files (This should also labeled with Category:Authentication if the passwords are used for authentication.)
* Lack of integrity protection for stored user data

{{Template:Stub}}

[[Category:Vulnerability]]

@@ Line 8: / Line 8: @@
 * Clear-text Passwords in configration files (This should also labeled with Category:Authentication if the passwords are used for authentication.)
 * Lack of integrity protection for stored user data
 {{Template:Stub}}
 [[Category:Vulnerability]]