Exposure of Sensitive System Information to an Unauthorized Control Sphere

Opis

The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.

Network-based products, such as web applications, often run on top of an operating system or similar environment. When the product communicates with outside parties, details about the underlying system are expected to remain hidden, such as path names for data files, other OS users, installed packages, the application environment, etc. This system information may be provided by the product itself, or buried within diagnostic or debugging messages. 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. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.

Skutki

• Confidentiality

  Read Application Data

Zapobieganie

• 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

Przykłady podatności

• CVE-2021-32638 Code analysis product passes access tokens as a command-line parameter or through an environment variable, making them visible to other processes via the ps command.

Słabość nadrzędna

• CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

Słabości podrzędne

• CWE-214 Invocation of Process Using Visible Sensitive Information
• CWE-548 Exposure of Information Through Directory Listing

Kiedy powstaje

• Implementation

Dotyczy

Not Language-Specific, Not Technology-Specific, Web Based

Źródła

1. Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors — Katrina Tsipenyuk, Brian Chess, Gary McGraw, NIST, 2005