Exposure of Resource to Wrong Sphere

Opis

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.

Skutki

• Confidentiality

  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.

• Integrity

  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.

• Other

  Varies by Context

  The consequences may vary widely depending on how the product uses the affected resource.

Słabość nadrzędna

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

Słabości podrzędne

• CWE-8 J2EE Misconfiguration: Entity Bean Declared Remote
• CWE-134 Use of Externally-Controlled Format String
• CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
• CWE-374 Passing Mutable Objects to an Untrusted Method
• CWE-375 Returning a Mutable Object to an Untrusted Caller
• CWE-377 Insecure Temporary File
• CWE-402 Transmission of Private Resources into a New Sphere ('Resource Leak')
• CWE-426 Untrusted Search Path
• CWE-427 Uncontrolled Search Path Element
• CWE-428 Unquoted Search Path or Element
• CWE-488 Exposure of Data Element to Wrong Session
• CWE-491 Public cloneable() Method Without Final ('Object Hijack')
• CWE-492 Use of Inner Class Containing Sensitive Data
• CWE-493 Critical Public Variable Without Final Modifier
• CWE-498 Cloneable Class Containing Sensitive Information
• CWE-499 Serializable Class Containing Sensitive Data
• CWE-522 Insufficiently Protected Credentials
• CWE-524 Use of Cache Containing Sensitive Information
• CWE-552 Files or Directories Accessible to External Parties
• CWE-582 Array Declared Public, Final, and Static
• CWE-583 finalize() Method Declared Public
• CWE-608 Struts: Non-private Field in ActionForm Class
• CWE-642 External Control of Critical State Data
• CWE-732 Incorrect Permission Assignment for Critical Resource
• CWE-767 Access to Critical Private Variable via Public Method
• CWE-927 Use of Implicit Intent for Sensitive Communication
• CWE-1189 Improper Isolation of Shared Resources on System-on-a-Chip (SoC)
• CWE-1282 Assumed-Immutable Data is Stored in Writable Memory
• CWE-1327 Binding to an Unrestricted IP Address
• CWE-1331 Improper Isolation of Shared Resources in Network On Chip (NoC)

Kiedy powstaje

• Architecture and Design
• Implementation — REALIZATION: This weakness is caused during implementation of an architectural security tactic.
• Operation

Dotyczy

Not Language-Specific

Uwagi

A "control sphere" is a set of resources and behaviors that are accessible to a single actor, or a group of actors. A product's security model will typically define multiple spheres, possibly implicitly. For example, a server might define one sphere for "administrators" who can create new user accounts with subdirectories under /home/server/, and a second sphere might cover the set of users who can create or delete files within their own subdirectories. A third sphere might be "users who are authenticated to the operating system on which the product is installed." Each sphere has different sets of actors and allowable behaviors.

Źródła

1. Supplemental Details - 2022 CWE Top 25 — MITRE, Details of Problematic Mappings, 2022