CWE-497 将系统数据暴露到未授权控制的范围

Exposure of System Data to an Unauthorized Control Sphere

结构: Simple

Abstraction: Variant

状态: Incomplete

被利用可能性: unkown

基本描述

Exposing system data or debugging information helps an adversary learn about the system and form an attack plan.

扩展描述

An information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. An attacker can also cause errors to occur by submitting unusual requests to the web application. The response to these errors can reveal detailed system information, deny service, cause security mechanisms to fail, and crash the server. An attacker can use error messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. An application may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.

适用平台

Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}

常见的影响

范围	影响	注释
Confidentiality	Read Application Data

可能的缓解方案

['Architecture and Design', 'Implementation']

策略:

Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user. All error message text should be HTML entity encoded before being written to the log file to protect against potential cross-site scripting attacks against the viewer of the logs

示例代码

例

The following code prints the path environment variable to the standard error stream:

bad C

char* path = getenv("PATH");
...
sprintf(stderr, "cannot find exe on path %s\n", path);

例

The following code prints an exception to the standard error stream:

bad Java

try {

...

} catch (Exception e) {

e.printStackTrace();

}

bad

try {

...

} catch (Exception e) {

Console.Writeline(e);

}

Depending upon the system configuration, this information can be dumped to a console, written to a log file, or exposed to a remote user. In some cases the error message tells the attacker precisely what sort of an attack the system will be vulnerable to. For example, a database error message can reveal that the application is vulnerable to a SQL injection attack. Other error messages can reveal more oblique clues about the system. In the example above, the search path could imply information about the type of operating system, the applications installed on the system, and the amount of care that the administrators have put into configuring the program.

例

The following code constructs a database connection string, uses it to create a new connection to the database, and prints it to the console.

bad C#

string cs="database=northwind; server=mySQLServer...";
SqlConnection conn=new SqlConnection(cs);
...
Console.Writeline(cs);

Depending on the system configuration, this information can be dumped to a console, written to a log file, or exposed to a remote user. In some cases the error message tells the attacker precisely what sort of an attack the system is vulnerable to. For example, a database error message can reveal that the application is vulnerable to a SQL injection attack. Other error messages can reveal more oblique clues about the system. In the example above, the search path could imply information about the type of operating system, the applications installed on the system, and the amount of care that the administrators have put into configuring the program.

分类映射

映射的分类名	ImNode ID	Mapped Node Name
7 Pernicious Kingdoms		System Information Leak
The CERT Oracle Secure Coding Standard for Java (2011)	ERR01-J	Do not allow exceptions to expose sensitive information
Software Fault Patterns	SFP23	Exposed Data

VULHUB ™