Skip to content

CWE-668: Exposure of Resource to Wrong Sphere

Class

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.

Consequences

  • Confidentiality: Read Application Data
  • Integrity: Modify Application Data
  • Other: Varies by Context

Recent advisories

  • GHSA-j8f7-rjxc-mr56 — filelock: ReadWriteLock follows a symlink at the lock path into SQLite
  • GHSA-ph72-cqr5-qpp7 — vLLM: Scale-out disaggregated multimodal transport trusts caller-supplied features
  • GHSA-fcqc-726x-5wfc — vm2: Sandboxed code can read and write host-realm memory via Node's shared Buffer pool
  • GHSA-h85j-hv3c-qfgq — vm2 exposes host HTTPS credentials and TLS traffic through globalAgent
  • GHSA-rpx2-p6hp-x5gj — SiYuan: Missing consistency check between packageName and repoURL/repoHash in bazaar package install allows overwriting an existing, trusted plugin
  • GHSA-596p-6jv8-775v — Craft CMS: Authenticated leak of secret environment variables
  • GHSA-r4w5-6pfg-jxp5 — Electron: ProtocolResponse.url reuses the default session cache instead of the registering session
  • GHSA-9cmh-xcqm-5hqr — n8n: Cross-Tenant Module-Cache Poisoning in the JS Task Runner
  • GHSA-9h85-g7w3-rh49 — ViewComponent: Reused Component Instances Retain Stale Render Context
  • GHSA-6jcq-6546-qrrw — PraisonAI SandlockSandbox falls back to unrestricted subprocess execution when Landlock is unavailable
  • GHSA-6c4r-g249-wv3c — OpenClaw: Sandboxed session spawn could expose the real workspace path to child prompts
  • GHSA-3q2p-72cj-682c — File Browser: Improper Access Control Occurs via Pre-Created Public Share for a Non-existent Path
  • GHSA-8396-jffm-qx4w — OpenFGA has cache-key delimiter injection in shared-iterator and v2 iterator that caches enables intra-store authorization-decision poisoning
  • GHSA-9g8x-92q2-p28f — NodeVM observability builtins leak host process and HTTP request data
  • GHSA-m7v2-7gxm-vc2v — Symfony has Unauthenticated PHP Object Deserialization in MonologBridge server:log Listener

All advisories for CWE-668

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor