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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

2783 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-2022-31066 Configuration API in EdgeXFoundry exposes message bus credentials to local unauthenticated users — edgex-go 5.9 Medium2022-06-14
CVE-2022-31046 Information Disclosure via Export Module in TYPO3 CMS — typo3 4.3 Medium2022-06-14
CVE-2022-29241 Known or guessable hidden files may be accessed in Jupyter Server — jupyter_server 7.1 High2022-06-14
CVE-2022-31060 Banner topic data is exposed on login-required Discourse sites — discourse 5.3 Medium2022-06-14
CVE-2022-29244 npm packing does not respect root-level ignore files in workspaces — npm 7.5 -2022-06-13
CVE-2022-1595 HC Custom WP-Admin URL <= 1.4 - Unauthenticated Secret URL Disclosure — HC Custom WP-Admin URL 7.5 -2022-06-13
CVE-2022-32741 Information disclosure in Request New Password feature — OTRS 5.3 Medium2022-06-13
CVE-2022-32740 Information disclosure in the External Interface — OTRS 3.5 Low2022-06-13
CVE-2022-32739 OTRS version number is always in the exported ICS files — OTRS 3.5 Low2022-06-13
CVE-2017-20031 PHPList information disclosure — PHPList 2.7 Low2022-06-10
CVE-2017-20022 Solare Solar-Log information disclosure — Solar-Log 7.5 -2022-06-09
CVE-2017-20019 Solare Solar-Log Config information disclosure — Solar-Log 4.3 Medium2022-06-09
CVE-2022-31051 Exposure of Sensitive Information to an Unauthorized Actor in semantic-release — semantic-release 4.4 Medium2022-06-09
CVE-2022-31033 Authorization header leak in rubygem Mechanize — mechanize 5.9 Medium2022-06-09
CVE-2019-25069 Axios Italia Axios RE Error Message ASP.NET information disclosure — Axios RE 5.3 Medium2022-06-09
CVE-2022-31042 Failure to strip the Cookie header on change in host or HTTP downgrade in Guzzle — guzzle 7.5 High2022-06-09
CVE-2022-31043 Fix failure to strip Authorization header on HTTP downgrade in Guzzle — guzzle 7.5 High2022-06-09
CVE-2022-30556 Information Disclosure in mod_lua with websockets — Apache HTTP Server--2022-06-08
CVE-2022-30743 Samsung Account 安全漏洞 — Samsung Account 5.3 Medium2022-06-07
CVE-2022-30742 Samsung mobile 日志信息泄露漏洞 — Find My Mobile 3.3 Low2022-06-07
CVE-2022-30741 Samsung mobile 日志信息泄露漏洞 — Find My Mobile 3.3 Low2022-06-07
CVE-2022-30740 Samsung Internet 安全漏洞 — Samsung Internet 4.1 Medium2022-06-07
CVE-2022-30737 Samsung Account 安全漏洞 — Samsung Account 4.0 Medium2022-06-07
CVE-2022-30736 Samsung Account 安全漏洞 — Samsung Account 5.3 Medium2022-06-07
CVE-2022-30735 Samsung Account 安全漏洞 — Samsung Account 5.9 Medium2022-06-07
CVE-2022-30734 Samsung Account 安全漏洞 — Samsung Account 4.0 Medium2022-06-07
CVE-2022-30733 Samsung Account 日志信息泄露漏洞 — Samsung Account 4.0 Medium2022-06-07
CVE-2022-30732 Samsung Account 安全漏洞 — Samsung Account 5.5 Medium2022-06-07
CVE-2022-28224 Calico and Calico Enterprise may be vulnerable to route hijacking with the floating IP feature — Calico Enterprise 5.5 Medium2022-06-06
CVE-2020-36532 Klapp App Authorization Credentials information disclosure — App 4.3 Medium2022-06-03

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