Improper Removal of Sensitive Information Before Storage or Transfer
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
Resources that may contain sensitive data include documents, packets, messages, databases, etc. While this data may be useful to an individual user or small set of users who share the resource, it may need to be removed before the resource can be shared outside of the trusted group. The process of removal is sometimes called cleansing or scrubbing. For example, a product for editing documents might not remove sensitive data such as reviewer comments or the local pathname where the document is stored. Or, a proxy might not remove an internal IP address from headers before making an outgoing request to an Internet site.
Impact: Read Files or DirectoriesRead Application Data
Sensitive data may be exposed to an unauthorized actor in another control sphere. This may have a wide range of secondary consequences which will depend on what data is exposed. One possibility is the exposure of system data allowing an attacker to craft a specific, more effective attack.
Strategy: Separation of Privilege
Strategy: Attack Surface Reduction
Effectiveness: Defense in Depth
ID : DX-220
This code either generates a public HTML user information page or a JSON response containing the same user information.Code Example:
// API flag, output JSON if set* $json = $_GET['json'] $username = $_GET['user'] if(!$json) { ``` $record = getUserRecord($username); foreach($record as $fieldName => $fieldValue) { if($fieldName == "email_address") {
php- PLOVER