Exposure of Resource to Wrong Sphere |
Weakness ID: 668 (Weakness Class) | Status: Draft |
Description Summary
Extended Description
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.
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 361 | Time and State | Development Concepts (primary)699 |
ChildOf | ![]() | 664 | Improper Control of a Resource Through its Lifetime | Research Concepts (primary)1000 |
ParentOf | ![]() | 8 | J2EE Misconfiguration: Entity Bean Declared Remote | Research Concepts (primary)1000 |
ParentOf | ![]() | 22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | Research Concepts1000 |
ParentOf | ![]() | 200 | Information Exposure | Research Concepts (primary)1000 |
ParentOf | ![]() | 220 | Sensitive Data Under FTP Root | Research Concepts (primary)1000 |
ParentOf | ![]() | 269 | Improper Privilege Management | Research Concepts1000 |
ParentOf | ![]() | 374 | Mutable Objects Passed by Reference | Research Concepts (primary)1000 |
ParentOf | ![]() | 375 | Passing Mutable Objects to an Untrusted Method | Research Concepts (primary)1000 |
ParentOf | ![]() | 377 | Insecure Temporary File | Research Concepts (primary)1000 |
ParentOf | ![]() | 402 | Transmission of Private Resources into a New Sphere ('Resource Leak') | Research Concepts (primary)1000 |
ParentOf | ![]() | 419 | Unprotected Primary Channel | Research Concepts (primary)1000 |
ParentOf | ![]() | 420 | Unprotected Alternate Channel | Research Concepts (primary)1000 |
ParentOf | ![]() | 427 | Uncontrolled Search Path Element | Research Concepts (primary)1000 |
ParentOf | ![]() | 428 | Unquoted Search Path or Element | Research Concepts (primary)1000 |
ParentOf | ![]() | 491 | Public cloneable() Method Without Final ('Object Hijack') | Research Concepts (primary)1000 |
ParentOf | ![]() | 492 | Use of Inner Class Containing Sensitive Data | Research Concepts (primary)1000 |
ParentOf | ![]() | 493 | Critical Public Variable Without Final Modifier | Research Concepts (primary)1000 |
ParentOf | ![]() | 522 | Insufficiently Protected Credentials | Research Concepts (primary)1000 |
ParentOf | ![]() | 552 | Files or Directories Accessible to External Parties | Research Concepts (primary)1000 |
ParentOf | ![]() | 582 | Array Declared Public, Final, and Static | Research Concepts (primary)1000 |
ParentOf | ![]() | 583 | finalize() Method Declared Public | Research Concepts (primary)1000 |
ParentOf | ![]() | 608 | Struts: Non-private Field in ActionForm Class | Research Concepts (primary)1000 |
ParentOf | ![]() | 642 | External Control of Critical State Data | Research Concepts (primary)1000 |
ParentOf | ![]() | 689 | Permission Race Condition During Resource Copy | Research Concepts (primary)1000 |
ParentOf | ![]() | 732 | Incorrect Permission Assignment for Critical Resource | Research Concepts (primary)1000 |
ParentOf | ![]() | 766 | Critical Variable Declared Public | Research Concepts (primary)1000 |
ParentOf | ![]() | 767 | Access to Critical Private Variable via Public Method | Research Concepts (primary)1000 |
CanFollow | ![]() | 219 | Sensitive Data Under Web Root | Research Concepts1000 |
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. |
Modifications | ||||
---|---|---|---|---|
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Eric Dalci | Cigital | External | |
updated Time of Introduction | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Relationships, Other Notes | ||||
2008-11-24 | CWE Content Team | MITRE | Internal | |
updated Relationships | ||||
2009-05-27 | CWE Content Team | MITRE | Internal | |
updated Relationships | ||||
2009-07-22 (Critical) | CWE Content Team | MITRE | Internal | |
Clarified description to include permissions. | ||||
2009-07-27 | CWE Content Team | MITRE | Internal | |
updated Description, Relationships | ||||
2009-10-29 | CWE Content Team | MITRE | Internal | |
updated Other Notes, Theoretical Notes | ||||
2009-12-28 | CWE Content Team | MITRE | Internal | |
updated Relationships |