Exposure of Resource to Wrong Sphere
This vulnerability occurs when an application unintentionally makes a resource accessible to users or systems that should not have permission to use it.
This flaw typically happens in two ways. First, a resource like a file or directory is given insecure permissions, allowing unauthorized users to read, modify, or delete it. Second, an application might fail to properly validate a user's request, allowing them to access resources outside their intended scope—like navigating to another user's private data or system files. In both scenarios, the core failure is a broken boundary. The application does not correctly enforce the separation between different trust zones, or 'control spheres.' This exposes sensitive data, configuration files, or system resources to the wrong audience, leading directly to data breaches, information leaks, or system compromise.
Impact: Read Application Data
An adversary that gains access to a resource exposed to a wrong sphere could potentially retrieve private data from that resource, thus breaking the intended confidentiality of that data.
Impact: Modify Application Data
An adversary that gains access to a resource exposed to a wrong sphere could potentially modify data held within that resource, thus breaking the intended integrity of that data and causing the system relying on that resource to make unintended decisions.
Impact: Varies by Context
The consequences may vary widely depending on how the product uses the affected resource.