用户工具

站点工具


cwe:cn:definition:200

CWE-200:信息暴露

Description Summary

An information exposure is the intentional or unintentional disclosure of information to an actor that is not explicitly authorized to have access to that information.

Extended Description

The information either

  1. is regarded as sensitive within the product's own functionality, such as a private message; or
  1. provides information about the product or its environment that could be useful in an attack but is normally not available to the attacker, such as the installation path of a product that is remotely accessible.

Many information exposures are resultant (e.g. PHP script error revealing the full path of the program), but they can also be primary (e.g. timing discrepancies in cryptography). There are many different types of problems that involve information exposures. Their severity can range widely depending on the type of information that is revealed.

Likelihood of Exploit

High

Common Consequences

Scope Technical Impace Note
ConfidentialityRead application data

Detection Methods

Detection Method - 1

Automated Static Analysis - Binary / Bytecode

According to SOAR, the following detection techniques may be useful:

Detection Method - 2

=== Dynamic Analysis with automated results interpretation === According to SOAR, the following detection techniques may be useful:

Detection Method - 3

Dynamic Analysis with manual results interpretation

According to SOAR, the following detection techniques may be useful:

Detection Method - 4

Manual Static Analysis - Source Code

According to SOAR, the following detection techniques may be useful:

Detection Method - 5

Automated Static Analysis - Source Code

According to SOAR, the following detection techniques may be useful:

Detection Method - 6

Architecture / Design Review

According to SOAR, the following detection techniques may be useful:

Potential Mitigations

Mitigation - 1

Architecture and Design

Strategy:Separation of Privilege

Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.

Ensure that appropriate compartmentalization is built into the system design and that the compartmentalization serves to allow for and further reinforce privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide when it is appropriate to use and to drop system privileges.

2013/05/30 12:46
cwe/cn/definition/200.txt · 最后更改: 2014/09/04 14:28 (外部编辑)