Privacy Leak through Data Queries |
Weakness ID: 202 (Weakness Variant) | Status: Draft |
Description Summary
Extended Description
In situations where data should not be tied to individual users, but a large number of users should be able to make queries that "scrub" the identity of users, it may be possible to get information about a user -- e.g., by specifying search terms that are known to be unique to that user.
Scope | Effect |
---|---|
Confidentiality | Sensitive information may possibly be leaked through data queries accidentally. |
This is a complex topic. See the book Translucent Databases for a good discussion of best practices. |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 200 | Information Exposure | Development Concepts (primary)699 |
ChildOf | ![]() | 359 | Privacy Violation | Research Concepts (primary)1000 |
CanAlsoBe | ![]() | 201 | Information Leak Through Sent Data | Research Concepts1000 |
Mapped Taxonomy Name | Node ID | Fit | Mapped Node Name |
---|---|---|---|
CLASP | Accidental leaking of sensitive information through data queries |
Submissions | ||||
---|---|---|---|---|
Submission Date | Submitter | Organization | Source | |
CLASP | Externally Mined | |||
Modifications | ||||
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Eric Dalci | Cigital | External | |
updated Time of Introduction | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Common Consequences, Description, Relationships, Taxonomy Mappings | ||||
Previous Entry Names | ||||
Change Date | Previous Entry Name | |||
2008-04-11 | Information Leak Through Data Queries | |||
Security-Database help your corporation foresee and avoid any security risks that may impact your IT infrastructure and business applications.