CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

• Confidentiality: Read Application Data

• [Architecture and Design] 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 the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

• Automated Static Analysis - Binary or Bytecode: According to SOAR [REF-1479], the following detection techniques may be useful: Cost effective for partial coverage: • Bytecode Weakness Analysis - including disassembler + source code weakness analysis • Inter-application Flow Analysis • Dynamic Analysis with Automated Results Interpretation: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Web Application Scanner • Web Services Scanner • Database Scanners • Dynamic Analysis with Manual Results Interpretation: According to SOAR [REF-1479], the following detection techniques may be useful: Cost effective for partial coverage: • Fuzz Tester • Framework-based Fuzzer • Automated Monitored Execution • Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious • Manual Static Analysis - Source Code: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Manual Source Code Review (not inspections) • Automated Static Analysis - Source Code: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Context-configured Source Code Weakness Analyzer Cost effective for partial coverage: • Source code Weakness Analyzer • Architecture or Design Review: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Formal Methods / Correct-By-Construction Cost effective for partial coverage: • Attack Modeling • Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)

• CVE-2022-31162: Rust library leaks Oauth client details in application debug logs • CVE-2021-25476: Digital Rights Management (DRM) capability for mobile platform leaks pointer information, simplifying ASLR bypass • CVE-2001-1483: Enumeration of valid usernames based on inconsistent responses • CVE-2001-1528: Account number enumeration via inconsistent responses. • CVE-2004-2150: User enumeration via discrepancies in error messages. • CVE-2005-1205: Telnet protocol allows servers to obtain sensitive environment information from clients. • CVE-2002-1725: Script calls phpinfo(), revealing system configuration to web user • CVE-2002-0515: Product sets a different TTL when a port is being filtered than when it is not being filtered, which allows remote attackers to identify filtered ports by comparing TTLs. • CVE-2004-0778: Version control system allows remote attackers to determine the existence of arbitrary files and directories via the -X command for an alternate history file, which causes different error messages to be returned. • CVE-2000-1117: Virtual machine allows malicious web site operators to determine the existence of files on the client by measuring delays in the execution of the getSystemResource method. • CVE-2003-0190: Product immediately sends an error message when a user does not exist, which allows remote attackers to determine valid usernames via a timing attack. • CVE-2008-2049: POP3 server reveals a password in an error message after multiple APOP commands are sent. Might be resultant from another weakness. • CVE-2007-5172: Program reveals password in error message if attacker can trigger certain database errors. • CVE-2008-4638: Composite: application running with high privileges (CWE-250) allows user to specify a restricted file to process, which generates a parsing error that leaks the contents of the file (CWE-209). • CVE-2007-1409: Direct request to library file in web application triggers pathname leak in error message. • CVE-2005-0603: Malformed regexp syntax leads to information exposure in error message. • CVE-2004-2268: Password exposed in debug information. • CVE-2003-1078: FTP client with debug option enabled shows password to the screen. • CVE-2022-0708: Collaboration platform does not clear team emails in a response, allowing leak of email addresses