引入方式
Architecture and Design : COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.
適用平台
程式語言
類別: Not Language-Specific (Undetermined)
常見後果
| 範圍 |
影響 |
可能性 |
Access Control Non-Repudiation | Hide Activities, Gain Privileges or Assume Identity | |
觀察到的案例
| 參考資料 |
描述 |
| S-bus functionality in a home automation product performs access control using an IP allowlist, which can be bypassed by a forged IP address. |
潛在緩解措施
Phases : Architecture and Design
Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate. While IP address verification can be a useful part of an authentication scheme, but it should not be the single factor required for authentication.
漏洞對應備注
理由說明 : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
備註 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
相關攻擊模式
| CAPEC ID |
攻擊模式名稱 |
| CAPEC-4 |
Using Alternative IP Address Encodings
This attack relies on the adversary using unexpected formats for representing IP addresses. Networked applications may expect network location information in a specific format, such as fully qualified domains names (FQDNs), URL, IP address, or IP Address ranges. If the location information is not validated against a variety of different possible encodings and formats, the adversary can use an alternate format to bypass application access control. |
參考資料
REF-18
The CLASP Application Security Process
Secure Software, Inc..
https://cwe.mitre.org/documents/sources/TheCLASPApplicationSecurityProcess.pdf REF-1371
IP address spoofing
https://en.wikipedia.org/wiki/IP_address_spoofing
提交
| 名稱 |
機構 |
日期 |
發布日期 |
Version |
| CLASP |
|
2006-07-19 +00:00 |
2006-07-19 +00:00 |
Draft 3 |
修改記錄
| 名稱 |
機構 |
日期 |
備註 |
| CWE Content Team |
MITRE |
2008-09-08 +00:00 |
updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings, Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2010-02-16 +00:00 |
updated Description, Other_Notes |
| CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences, Demonstrative_Examples |
| CWE Content Team |
MITRE |
2012-05-11 +00:00 |
updated Demonstrative_Examples, Relationships |
| CWE Content Team |
MITRE |
2013-06-23 +00:00 |
Changed type from composite to weakness. |
| CWE Content Team |
MITRE |
2013-07-17 +00:00 |
updated Applicable_Platforms, Description, Name, Relationships, Type |
| CWE Content Team |
MITRE |
2014-02-18 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2017-11-08 +00:00 |
updated Causal_Nature, Demonstrative_Examples, Modes_of_Introduction, Relationships |
| CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated References, Relationships |
| CWE Content Team |
MITRE |
2023-01-31 +00:00 |
updated Description |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2023-10-26 +00:00 |
updated Observed_Examples, References |
| CWE Content Team |
MITRE |
2025-04-03 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Common_Consequences, Description, Potential_Mitigations |