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

Goal: 1000 CNY · Raised: 1110 CNY

100%

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

2799 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-2024-21380 Microsoft Dynamics Business Central/NAV Information Disclosure Vulnerability — Microsoft Dynamics 365 Business Central 2022 Release Wave 2 8.0 High2024-02-13
CVE-2022-22506 IBM Robotic Process Automation information disclosure — Robotic Process Automation 4.6 Medium2024-02-12
CVE-2024-1431 Netgear R7000 Web Management Interface debuginfo.htm information disclosure — R7000 4.3 Medium2024-02-11
CVE-2024-1430 Netgear R7000 Web Management Interface currentsetting.htm information disclosure — R7000 4.3 Medium2024-02-11
CVE-2024-1406 Linksys WRT54GL Web Management Interface SysInfo1.htm information disclosure — WRT54GL 4.3 Medium2024-02-10
CVE-2024-1405 Linksys WRT54GL Web Management Interface wlaninfo.htm information disclosure — WRT54GL 4.3 Medium2024-02-10
CVE-2024-1404 Linksys WRT54GL Web Management Interface SysInfo.htm information disclosure — WRT54GL 4.3 Medium2024-02-09
CVE-2024-21624 Potential Information Leak in User-Constructed Message Templates in nonebot2 — nonebot2 5.7 Medium2024-02-09
CVE-2023-50298 Apache Solr: Solr can expose ZooKeeper credentials via Streaming Expressions — Apache Solr 7.5 -2024-02-09
CVE-2024-24825 TokenManager not checking permissions on cached tokens in DIRAC — DIRAC 9.1 Critical2024-02-08
CVE-2024-0242 Unauthorized access to settings in Qolsys IQ Panel 4 and IQ4 Hub — IQ Panel 4 7.3 High2024-02-08
CVE-2024-1255 sepidz SepidzDigitalMenu Waiters information disclosure — SepidzDigitalMenu 5.3 Medium2024-02-06
CVE-2024-22331 IBM UrbanCode Deploy information disclosure — UrbanCode Deploy 6.2 Medium2024-02-06
CVE-2023-46183 IBM PowerVM Hypervisor information disclosure — PowerVM Hypervisor 5.3 Medium2024-02-06
CVE-2024-23344 Tuleap's content of artifacts might be readable by unauthorized users — tuleap 5.3 Medium2024-02-06
CVE-2024-1208 LearnDash LMS <= 4.10.2 - Sensitive Information Exposure via API — LearnDash LMS 5.3 Medium2024-02-05
CVE-2024-1209 LearnDash LMS <= 4.10.1 - Sensitive Information Exposure via assignments — LearnDash LMS 5.3 Medium2024-02-05
CVE-2024-1210 LearnDash LMS <= 4.10.1 - Sensitive Information Exposure via API — LearnDash LMS 5.3 Medium2024-02-05
CVE-2023-33851 IBM PowerVM Hypervisor information disclosure — PowerVM Hypervisor 5.3 Medium2024-02-04
CVE-2024-0909 Anonymous Restricted Content <= 1.6.2 - Protection Mechanism Bypass — Anonymous Restricted Content 5.3 Medium2024-02-03
CVE-2024-1200 Jspxcms information disclosure — Jspxcms 5.3 Medium2024-02-03
CVE-2024-24757 open-irs .env Exposure — open-irs 7.6 High2024-02-02
CVE-2024-24755 discourse-group-membership-ip-block is exposing potentially sensitive custom fields — discourse-group-membership-ip-block 4.3 Medium2024-02-01
CVE-2024-1098 Rebuild proxy-download QiniuCloud.getStorageFile information disclosure — Rebuild 4.3 Medium2024-01-31
CVE-2023-44312 Apache ServiceComb Service-Center: attacker can query all environment variables of the service-center server — Apache ServiceComb Service-Center 5.8 Medium2024-01-31
CVE-2024-22200 vantage6-UI docker image leaks software version information — vantage6-UI 3.3 Low2024-01-30
CVE-2024-1033 openBI Datament.php agent information disclosure — openBI 4.3 Medium2024-01-30
CVE-2023-52187 WordPress Image Source Control Plugin <= 2.17.0 is vulnerable to Sensitive Data Exposure — Image Source Control Lite – Show Image Credits and Captions 5.3 Medium2024-01-26
CVE-2024-22141 WordPress Profile Builder Pro Plugin <= 3.10.0 is vulnerable to Sensitive Data Exposure — Profile Builder Pro 6.5 Medium2024-01-24
CVE-2024-22154 WordPress SalesKing Plugin <= 1.6.15 is vulnerable to Sensitive Data Exposure — SalesKing 7.5 High2024-01-24

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