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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-532 (通过日志文件的信息暴露) — Vulnerability Class 770

770 vulnerabilities classified as CWE-532 (通过日志文件的信息暴露). AI Chinese analysis included.

CWE-532 represents a critical information disclosure weakness where software inadvertently records sensitive data, such as passwords, credit card numbers, or personal identifiers, into log files. This vulnerability is typically exploited by attackers who gain access to these logs through insufficient file permissions, insecure storage practices, or compromised administrative accounts. Once accessed, the exposed data can be harvested for identity theft, financial fraud, or further system intrusion. To prevent this, developers must implement strict data sanitization protocols, ensuring that sensitive fields are masked or excluded before logging. Additionally, employing robust access controls and encryption for log storage, alongside regular audits of logging configurations, helps mitigate the risk of accidental exposure. By treating log files as potential repositories of confidential information, organizations can significantly reduce their attack surface and maintain compliance with data protection standards.

MITRE CWE Description
The product writes sensitive information to a log file.
Common Consequences (1)
Confidentiality Read Application Data
Logging sensitive user data, full path names, or system information often provides attackers with an additional, less-protected path to acquiring the information.
Mitigations (4)
Architecture and Design, Implementation Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution Remove debug log files before deploying the application into production.
Operation Protect log files against unauthorized read/write.
Implementation Adjust configurations appropriately when software is transitioned from a debug state to production.
Examples (2)
In the following code snippet, a user's full name and credit card number are written to a log file.
logger.info("Username: " + usernme + ", CCN: " + ccn);
Bad · Java
This code stores location information about the current user:
locationClient = new LocationClient(this, this, this); locationClient.connect(); currentUser.setLocation(locationClient.getLastLocation()); ... catch (Exception e) { AlertDialog.Builder builder = new AlertDialog.Builder(this); builder.setMessage("Sorry, this application has experienced an error."); AlertDialog alert = builder.create(); alert.show(); Log.e("ExampleActivity", "Caught exception: " + e + " While on User:" + User.toString()); }
Bad · Java
CVE ID Title CVSS Severity Published
CVE-2025-54064 rucio-server, rucio-ui, and rucio-webui vulnerable to insertion of X-Rucio-Auth-Token in apache access logfiles — helm-charts 7.5AI High AI 2025-07-17
CVE-2025-30483 Dell ECS和Dell ObjectScale 日志信息泄露漏洞 — ECS 5.5 Medium 2025-07-15
CVE-2025-53885 Directus doesn't redact sensitive user data when logging via event hooks — directus 4.2 Medium 2025-07-14
CVE-2025-6392 Daily Data Dump Collector logs database password in cleartext when running docker exec commands (CVE-2025-6392) — Brocade SANnav 6.2AI Medium AI 2025-07-10
CVE-2025-36599 Dell PowerFlex Manager VM 日志信息泄露漏洞 — PowerFlex Manager VM 4.3 Medium 2025-07-09
CVE-2025-5464 Ivanti Connect Secure 日志信息泄露漏洞 — Connect Secure 6.5 Medium 2025-07-08
CVE-2025-5463 Ivanti Connect Secure 日志信息泄露漏洞 — Connect Secure 5.5 Medium 2025-07-08
CVE-2025-6711 Incomplete Redaction of Sensitive Information in MongoDB Server Logs — MongoDB Server 4.4 Medium 2025-07-07
CVE-2024-9453 Jenkins-image: sensitive data disclosure when using openshift jenkins image — openshift-sync-plugin 6.5 Medium 2025-07-04
CVE-2025-6587 Exposure of system environment variables in Docker Desktop diagnostic logs — Docker Desktop 6.5AI Medium AI 2025-07-03
CVE-2025-6624 Snyk CLI 安全漏洞 — snyk 7.2 High 2025-06-26
CVE-2025-52893 OpenBao May Leak Sensitive Information in Logs When Processing Malformed Data — openbao 4.5 Medium 2025-06-25
CVE-2024-7586 Insertion of Sensitive Information into Log File in GitLab — GitLab 4.1 Medium 2025-06-20
CVE-2025-36050 IBM QRadar SIEM information disclosure — QRadar SIEM 6.2 Medium 2025-06-19
CVE-2025-50200 RabbitMQ Node can log Basic Auth header from an HTTP request — rabbitmq-server 6.8AI Medium AI 2025-06-19
CVE-2025-2327 FlashArray KEK Logging Vulnerability — FlashArray 7.5AI High AI 2025-06-16
CVE-2025-36573 Dell Smart Dock Firmware 日志信息泄露漏洞 — Smart Dock 7.1 High 2025-06-12
CVE-2025-49009 Para Inserts Sensitive Information into Log File for Facebook authentication — para 6.2 Medium 2025-06-05
CVE-2025-48493 Yii 2 Redis may expose AUTH paramters in logs in case of connection failure — yii2-redis 6.5AI Medium AI 2025-06-05
CVE-2025-48955 Para Server Logs Sensitive Information — para 6.2 Medium 2025-06-02
CVE-2025-46777 Fortinet FortiPortal 日志信息泄露漏洞 — FortiPortal 2.2 Low 2025-05-28
CVE-2025-48374 zot logs secrets — zot 6.5AI Medium AI 2025-05-22
CVE-2025-3911 Exposure in Docker Desktop logs of environment variables configured for running containers — Docker Desktop 5.5AI Medium AI 2025-04-29
CVE-2025-46329 Snowflake Connector for C/C++ inserts client-side encryption key in DEBUG logs — libsnowflakeclient 3.3 Low 2025-04-29
CVE-2025-46614 Snowflake ODBC Driver 安全漏洞 — Snowflake ODBC 3.3 Low 2025-04-28
CVE-2025-46432 JetBrains TeamCity 日志信息泄露漏洞 — TeamCity 4.3 Medium 2025-04-25
CVE-2025-2092 Remote site authentication secrets written to web log — Checkmk 7.5 - 2025-04-22
CVE-2025-2300 Information exposure vulnerability in Hitachi Ops Center Common Services within Hitachi Ops Center OVA — Hitachi Ops Center Common Services 5.5 Medium 2025-04-22
CVE-2025-24651 WordPress WebToffee WP Backup and Migration plugin <= 1.5.3 - Sensitive Data Exposure vulnerability — WordPress Backup & Migration 5.9 Medium 2025-04-17
CVE-2025-32382 Snowflake credentials logged by the Metabase backend — metabase 8.1AI High AI 2025-04-10

Vulnerabilities classified as CWE-532 (通过日志文件的信息暴露) represent 770 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.