CWE-673 詳細

The product does not prevent the definition of control spheres from external actors.

Typically, a product defines its control sphere within the code itself, or through configuration by the product's administrator. In some cases, an external party can change the definition of the control sphere.

導入モード

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

適用可能なプラットフォーム

言語

クラス： Not Language-Specific (Undetermined)

一般的な結果

観察された例

脆弱性マッピングノート

理由 : This CWE entry is a Class and might have Base-level children that would be more appropriate
コメント : Examine children of this entry to see if there is a better fit

ノート

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.

登録情報

変更履歴