Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1310 CNY

100%

CWE-200 (信息暴露) — Vulnerability Class 2822

2822 vulnerabilities classified as CWE-200 (信息暴露). AI Chinese analysis included.

CWE-200 represents a critical information disclosure weakness where software inadvertently reveals sensitive data to unauthorized entities. This vulnerability is typically exploited by attackers who leverage insufficient access controls, insecure direct object references, or verbose error messages to harvest credentials, personal identifiable information, or internal system details. By analyzing network traffic or manipulating application inputs, adversaries can extract this exposed data to facilitate further attacks, such as identity theft or privilege escalation. To mitigate this risk, developers must implement strict access control mechanisms, ensuring that data retrieval is validated against user permissions. Additionally, employing robust encryption for data at rest and in transit, along with sanitizing error outputs to prevent information leakage, significantly reduces the attack surface. Regular security audits and adherence to the principle of least privilege further ensure that sensitive information remains protected from unauthorized exposure.

MITRE CWE Description
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include: private, personal information, such as personal messages, financial data, health records, geographic location, or contact details system status and environment, such as the operating system and installed packages business secrets and intellectual property network status and configuration the product's own code or internal state metadata, e.g. logging of connections or message headers indirect information, such as a discrepancy between two internal operations that can be observed by an outsider Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include: the product's own users people or organizations whose information is created or used by the product, even if they are not direct product users the product's administrators, including the admins of the system(s) and/or networks on which the product operates the developer Information exposures can occur in different ways: the code explicitly inserts sensitive information into …
Common Consequences (1)
ConfidentialityRead Application Data
Mitigations (1)
Architecture and DesignCompartmentalize 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 separatio…
Examples (2)
The following code checks validity of the supplied username and password and notifies the user of a successful or failed login.
my $username=param('username'); my $password=param('password'); if (IsValidUsername($username) == 1) { if (IsValidPassword($username, $password) == 1) { print "Login Successful"; } else { print "Login Failed - incorrect password"; } } else { print "Login Failed - unknown username"; }
Bad · Perl
"Login Failed - incorrect username or password"
Result
This code tries to open a database connection, and prints any exceptions that occur.
try { openDbConnection(); } //print exception message that includes exception message and configuration file location catch (Exception $e) { echo 'Caught exception: ', $e->getMessage(), '\n'; echo 'Check credentials in config file at: ', $Mysql_config_location, '\n'; }
Bad · PHP
CVE IDTitleCVSSSeverityPublished
CVE-2023-43754 Permalink previews displayed for posts in archived channels even if users are disallowed to view archived channels — Mattermost 4.3 Medium2023-11-27
CVE-2023-45223 Users full name disclosure through Mattermost Boards with Show Full Name Option disabled — Mattermost 4.3 Medium2023-11-27
CVE-2023-48796 Apache dolphinscheduler sensitive information disclosure — Apache DolphinScheduler 7.5 -2023-11-24
CVE-2021-39008 IBM QRadar WinCollect Agent information disclosure — QRadar WinCollect Agent 2.7 Low2023-11-23
CVE-2023-47244 WordPress Email Marketing for WooCommerce by Omnisend Plugin <= 1.13.8 is vulnerable to Sensitive Data Exposure — Email Marketing for WooCommerce by Omnisend 5.3 Medium2023-11-23
CVE-2023-47529 WordPress Cloud Templates & Patterns collection Plugin <= 1.2.2 is vulnerable to Sensitive Data Exposure — Cloud Templates & Patterns collection 5.3 Medium2023-11-23
CVE-2023-41786 Database backups availability by low-privileged users — Pandora FMS 6.8 Medium2023-11-23
CVE-2023-43123 Apache Storm: Local Information Disclosure Vulnerability in Storm-core on Unix-Like systems due temporary files — Apache Storm 5.5 -2023-11-23
CVE-2023-47668 WordPress Restrict Content Plugin <= 3.2.7 is vulnerable to Sensitive Data Exposure — Membership Plugin – Restrict Content 5.3 Medium2023-11-23
CVE-2023-40002 WordPress Booster for WooCommerce Plugin <= 7.1.1 is vulnerable to Sensitive Data Exposure — Booster for WooCommerce 6.5 Medium2023-11-22
CVE-2023-23978 WordPress WP Client Reports Plugin <= 1.0.16 is vulnerable to Sensitive Data Exposure — WP Client Reports 4.3 Medium2023-11-22
CVE-2022-36777 IBM Cloud Pak for Security information disclosure — Cloud Pak for Security 4.3 Medium2023-11-22
CVE-2023-2446 UserPro <= 5.1.1 - Sensitive Information Disclosure via Shortcode — UserPro - Community and User Profile WordPress Plugin 6.5 Medium2023-11-22
CVE-2021-22143 Elastic APM .NET Agent information disclosure — Elastic APM .NET Agent 2.1 Low2023-11-22
CVE-2023-47643 SuiteCRM has Unauthenticated Graphql Introspection Enabled — SuiteCRM-Core 3.1 Low2023-11-21
CVE-2023-48294 Broken Access control on Graphs Feature in LibreNMS — librenms 4.3 Medium2023-11-17
CVE-2023-47642 Stream description leaks to ex-subscribers in Zulip — zulip 4.3 Medium2023-11-16
CVE-2023-6105 ManageEngine Information Disclosure in Multiple Products — Service Desk Plus 5.5 Medium2023-11-15
CVE-2023-47126 Information Disclosure in Install Tool in typo3/cms-install — typo3 3.7 Low2023-11-14
CVE-2023-41676 Fortinet FortiSIEM 安全漏洞 — FortiSIEM 4.2 Medium2023-11-14
CVE-2023-36043 Open Management Infrastructure Information Disclosure Vulnerability — System Center Operations Manager (SCOM) 2022 6.5 Medium2023-11-14
CVE-2023-47117 Object Relational Mapper Leak Vulnerability in Filtering Task in Label Studio — label-studio 7.5 High2023-11-13
CVE-2023-6101 Maiwei Safety Production Control Platform Intelligent Monitoring ha.html information disclosure — Safety Production Control Platform 5.3 Medium2023-11-13
CVE-2023-6100 Maiwei Safety Production Control Platform GetItemList information disclosure — Safety Production Control Platform 5.3 Medium2023-11-13
CVE-2023-42781 Apache Airflow: Permission verification bypass allows viewing dagruns of other dags — Apache Airflow 4.3 -2023-11-12
CVE-2023-47614 Telit多款产品安全漏洞 — BGS5 3.3 Low2023-11-10
CVE-2023-6076 PHPGurukul Restaurant Table Booking System Reservation Status booking-details.php information disclosure — Restaurant Table Booking System 5.3 Medium2023-11-10
CVE-2023-45816 Unread bookmark reminder notifications that the user cannot access can be seen — discourse 3.3 Low2023-11-10
CVE-2018-8863 Philips EncoreAnywhere Exposure of Sensitive Information to an Unauthorized Actor — EncoreAnywhere 5.9 Medium2023-11-09
CVE-2023-5551 Moodle: forum summary report shows students from other groups when in separate groups mode 3.3 Low2023-11-09

Vulnerabilities classified as CWE-200 (信息暴露) represent 2822 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.