Modes d'introduction
Implementation
Plateformes applicables
Langue
Class: Not Language-Specific (Undetermined)
Technologies
Class: Not Technology-Specific (Undetermined)
Class: Web Based (Undetermined)
Conséquences courantes
| Portée |
Impact |
Probabilité |
Confidentiality Integrity | Read Files or Directories, Modify Files or Directories | |
Exemples observés
| Références |
Description |
| read files via "/........../" in URL |
| read files via "...." in web server |
| read files via "......" in web server (doubled triple dot?) |
| read files via "......" in web server (doubled triple dot?) |
| multiple attacks using "..", "...", and "...." in different commands |
| "..." or "...." in chat server |
Mesures d’atténuation potentielles
Phases : Implementation
Phases : Implementation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Méthodes de détection
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.)
Notes de cartographie des vulnérabilités
Justification : 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.
Commentaire : 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.
Notes
Like the triple-dot CWE-32, this manipulation probably hides multiple weaknesses that should be made more explicit.
Soumission
| Nom |
Organisation |
Date |
Date de publication |
Version |
| PLOVER |
|
2006-07-19 +00:00 |
2006-07-19 +00:00 |
Draft 3 |
Modifications
| Nom |
Organisation |
Date |
Commentaire |
| Eric Dalci |
Cigital |
2008-07-01 +00:00 |
updated Potential_Mitigations, Time_of_Introduction |
| CWE Content Team |
MITRE |
2008-09-08 +00:00 |
updated Maintenance_Notes, Relationships, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2008-10-14 +00:00 |
updated Description, Maintenance_Notes |
| CWE Content Team |
MITRE |
2009-07-27 +00:00 |
updated Potential_Mitigations |
| CWE Content Team |
MITRE |
2010-06-21 +00:00 |
updated Description, Potential_Mitigations |
| CWE Content Team |
MITRE |
2011-03-29 +00:00 |
updated Potential_Mitigations |
| CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences |
| CWE Content Team |
MITRE |
2012-05-11 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2014-07-30 +00:00 |
updated Relationships, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2017-11-08 +00:00 |
updated Applicable_Platforms |
| CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated Potential_Mitigations, Relationships |
| CWE Content Team |
MITRE |
2020-06-25 +00:00 |
updated Potential_Mitigations |
| CWE Content Team |
MITRE |
2021-03-15 +00:00 |
updated Potential_Mitigations |
| 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 |
2025-09-09 +00:00 |
updated Affected_Resources, Functional_Areas |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Applicable_Platforms, Detection_Factors, Weakness_Ordinalities |