1. Home
  2. CWE Database
  3. CWE-668
Class · High

CWE-668: Exposure of Resource to Wrong Sphere

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

CWE-668 · Class Level

Description

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.

Potential Impact

Confidentiality

Read Application Data

Integrity

Modify Application Data

Other

Varies by Context

CWE-664: Improper Control of a Resource Through its Lifetime

The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use,...

Frequently Asked Questions

What is CWE-668?

CWE-668 (Exposure of Resource to Wrong Sphere) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Class-level weakness. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

How can CWE-668 be exploited?

Attackers can exploit CWE-668 (Exposure of Resource to Wrong Sphere) to read application data. This weakness is typically introduced during the Architecture and Design, Implementation, Operation phase of software development.

How do I prevent CWE-668?

Follow secure coding practices, conduct code reviews, and use automated security testing tools (SAST/DAST) to detect this weakness early in the development lifecycle.

What is the severity of CWE-668?

CWE-668 is classified as a Class-level weakness (High abstraction). Its actual severity depends on the specific context and how the weakness manifests in your application.