CWE-528: Exposure of Core Dump File to an Unauthorized Control Sphere
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.
View on MITRETechnical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
Phase
Description
Protect the core dump files from unauthorized access.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
No examples or observed CVEs available for this CWE.
CWE Relationships
No relationship information available for this CWE.
Frequently Asked Questions
What is CWE-528: Exposure of Core Dump File to an Unauthorized Control Sphere?+
CWE-528: Exposure of Core Dump File to an Unauthorized Control Sphere is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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 are the security consequences of Exposure of Core Dump File to an Unauthorized Control Sphere?+
If exploited, CWE-528 (Exposure of Core Dump File to an Unauthorized Control Sphere) it can compromise Confidentiality, leading to outcomes such as Read Application Data and Read Files or Directories.
How do you prevent or mitigate Exposure of Core Dump File to an Unauthorized Control Sphere?+
Recommended mitigations for CWE-528 include: Protect the core dump files from unauthorized access.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-528 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.