CWE-274
Improper Handling of Insufficient Privileges
2006-07-19
00h00 +00:00
00h00 +00:00
特定のCWEの通知
特定のCWEの変更情報をいち早くお届けします。
名前: Improper Handling of Insufficient Privileges
The product does not handle or incorrectly handles when it has insufficient privileges to perform an operation.
一般情報
導入モード
Implementation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.Operation
適用可能なプラットフォーム
言語
クラス： Not Language-Specific (Undetermined)一般的な結果
| スコープ | 影響 | 可能性 |
|---|---|---|
| Other | Other, Alter Execution Logic 注記：This can lead to resultant weaknesses. |
観察された例
| 参考文献 | 説明 |
|---|---|
CVE-2001-1564 | System limits are not properly enforced after privileges are dropped. |
CVE-2005-3286 | Firewall crashes when it can't read a critical memory block that was protected by a malicious process. |
CVE-2005-1641 | Does not give admin sufficient privileges to overcome otherwise legitimate user actions. |
検出方法
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)有効性 : High
脆弱性マッピングノート
理由 : This CWE entry could be deprecated in a future version of CWE.コメント : See maintenance notes.
ノート
CWE-280 and CWE-274 are too similar. It is likely that CWE-274 will be deprecated in the future.Overlaps dropped privileges, insufficient permissions.
This has a layering relationship with Unchecked Error Condition and Unchecked Return Value.
Within the context of vulnerability theory, privileges and permissions are two sides of the same coin. Privileges are associated with actors, and permissions are associated with resources. To perform access control, at some point the product makes a decision about whether the actor (and the privileges that have been assigned to that actor) is allowed to access the resource (based on the permissions that have been specified for that resource).
登録情報
| 名前 | 組織 | 日付 | リリース日 | Version |
|---|---|---|---|---|
| PLOVER | Draft 3 |
変更履歴
| 名前 | 組織 | 日付 | コメント |
|---|---|---|---|
| Eric Dalci | Cigital | updated Time_of_Introduction | |
| CWE Content Team | MITRE | updated Description, Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Maintenance_Notes, Theoretical_Notes | |
| CWE Content Team | MITRE | updated Description, Name | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Causal_Nature, Modes_of_Introduction, Relationships | |
| CWE Content Team | MITRE | updated Relationship_Notes, Theoretical_Notes | |
| CWE Content Team | MITRE | updated Description, Relationships, Theoretical_Notes | |
| CWE Content Team | MITRE | updated Detection_Factors, Relationships, Time_of_Introduction | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Common_Consequences, Description |
