- What is CWE-528?
- The product generates a core dump file in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.
- What CVEs are caused by CWE-528?
- 2 recorded CVEs are attributed to CWE-528, including CVE-2025-48928, CVE-2024-10403. 1 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
- How do you prevent CWE-528?
- Protect the core dump files from unauthorized access.
- How is CWE-528 detected?
- Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
- What are the consequences of CWE-528?
- Exploiting CWE-528 can lead to: Read Application Data, Read Files or Directories.
- Is CWE-528 actively exploited?
- Yes. 1 CWE-528 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 2 recorded CVEs.