취약점 도입 방식
Implementation : This can happen when the product automatically
"determines" the type of the object even if it is
contradictory to an explicitly specified type.
적용 가능한 플랫폼
언어
클래스: Not Language-Specific (Undetermined)
기술
클래스: Not Technology-Specific (Undetermined)
클래스: Web Based (Often)
일반적인 결과
| 범위 |
영향 |
가능성 |
Integrity Other | Varies by Context, Unexpected State
참고: An example of deploying the wrong handler would be calling a servlet to reveal source code of a .JSP file, or | |
관찰된 예시
| 참고 자료 |
설명 |
| Source code disclosure via manipulated file extension that causes parsing by wrong DLL. |
| Web browser does not properly handle the Content-Type header field, causing a different application to process the document. |
| Source code disclosure by directly invoking a servlet. |
| Arbitrary Perl functions can be loaded by calling a non-existent function that activates a handler. |
잠재적 완화 방법
Phases : Architecture and Design
Perform a type check before interpreting an object.
Phases : Architecture and Design
Reject any inconsistent types, such as a file with a .GIF extension that appears to consist of PHP code.
취약점 매핑 메모
근거 : This CWE entry is at the Base 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-11 |
Cause Web Server Misclassification
An attack of this type exploits a Web server's decision to take action based on filename or file extension. Because different file types are handled by different server processes, misclassification may force the Web server to take unexpected action, or expected actions in an unexpected sequence. This may cause the server to exhaust resources, supply debug or system data to the attacker, or bind an attacker to a remote process. |
참고 자료
REF-62
The Art of Software Security Assessment
Mark Dowd, John McDonald, Justin Schuh.
제출
| 이름 |
조직 |
날짜 |
출시일 |
Version |
| PLOVER |
|
2006-07-19 +00:00 |
2006-07-19 +00:00 |
Draft 3 |
수정 사항
| 이름 |
조직 |
날짜 |
댓글 |
| Eric Dalci |
Cigital |
2008-07-01 +00:00 |
updated Potential_Mitigations, Time_of_Introduction |
| CWE Content Team |
MITRE |
2008-09-08 +00:00 |
updated Relationships, Other_Notes, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2008-10-14 +00:00 |
updated Description |
| CWE Content Team |
MITRE |
2009-10-29 +00:00 |
updated Other_Notes, Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences |
| CWE Content Team |
MITRE |
2011-06-27 +00:00 |
updated Common_Consequences |
| CWE Content Team |
MITRE |
2012-05-11 +00:00 |
updated References, Relationships |
| CWE Content Team |
MITRE |
2012-10-30 +00:00 |
updated Potential_Mitigations |
| CWE Content Team |
MITRE |
2014-07-30 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2017-11-08 +00:00 |
updated Applicable_Platforms |
| CWE Content Team |
MITRE |
2019-06-20 +00:00 |
updated Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2021-10-28 +00:00 |
updated Relationships |
| 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 |
2025-12-11 +00:00 |
updated Applicable_Platforms |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Applicable_Platforms, Common_Consequences, Description, Dimensions, Modes_of_Introduction |