이름: Not Failing Securely
When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.
일반 정보
취약점 도입 방식
Architecture and Design : This weakness typically occurs as a result of wanting to "fail functional" to minimize administration and support costs, instead of "failing safe."Implementation
적용 가능한 플랫폼
언어
클래스: Not Language-Specific (Undetermined)기술
클래스: Not Technology-Specific (Undetermined)클래스: ICS/OT (Undetermined)
일반적인 결과
| 범위 | 영향 | 가능성 |
|---|---|---|
| Other | Varies by Context 참고: By entering a less secure state, the product inherits the weaknesses associated with that state, making it easier to compromise. At the least, it causes administrators to have a false sense of security. | |
| Access Control | Bypass Protection Mechanism 참고: Intended access restrictions can be bypassed, which is often contradictory to what the product's administrator expects. |
관찰된 예시
| 참고 자료 | 설명 |
|---|---|
CVE-2007-5277 | The failure of connection attempts in a web browser resets DNS pin restrictions. An attacker can then bypass the same origin policy by rebinding a domain name to a different IP address. This was an attempt to "fail functional." |
CVE-2006-4407 | Incorrect prioritization leads to the selection of a weaker cipher. Although it is not known whether this issue occurred in implementation or design, it is feasible that a poorly designed algorithm could be a factor. |
잠재적 완화 방법
Phases : Architecture and DesignSubdivide and allocate resources and components so that a failure in one part does not affect the entire product.
취약점 매핑 메모
근거 : 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
메모
Since design issues are hard to fix, they are rarely publicly reported, so there are few CVE examples of this problem as of January 2008. Most publicly reported issues occur as the result of an implementation error instead of design, such as CVE-2005-3177 (Improper handling of large numbers of resources) or CVE-2005-2969 (inadvertently disabling a verification step, leading to selection of a weaker protocol).참고 자료
REF-196
The Protection of Information in Computer SystemsJerome H. Saltzer, Michael D. Schroeder.
http://web.mit.edu/Saltzer/www/publications/protection/
REF-522
Failing SecurelySean Barnum, Michael Gegick.
https://web.archive.org/web/20221017053210/https://www.cisa.gov/uscert/bsi/articles/knowledge/principles/failing-securely
제출
| 이름 | 조직 | 날짜 | 출시일 | Version |
|---|---|---|---|---|
| Pascal Meunier | Purdue University | Draft 8 |
수정 사항
| 이름 | 조직 | 날짜 | 댓글 |
|---|---|---|---|
| Eric Dalci | Cigital | updated Time_of_Introduction | |
| CWE Content Team | MITRE | updated Common_Consequences, Description, Name, Relationships, Taxonomy_Mappings, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Description, Name | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Name | |
| CWE Content Team | MITRE | updated Research_Gaps | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Potential_Mitigations | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Causal_Nature, Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated References | |
| CWE Content Team | MITRE | updated Applicable_Platforms | |
| CWE Content Team | MITRE | updated References, Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Common_Consequences, Description, Modes_of_Introduction, Name |
