This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Path Issue - dot dot backslash"
From OWASP
Weilin Zhong (talk | contribs) |
(Reverting to last version not containing links to s1.shard.jp) |
||
| (16 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{template:CandidateForDeletion}} |
| + | |||
| + | #REDIRECT [[Failure_to_follow_guideline/specification]] | ||
| + | |||
| + | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| + | |||
==Description== | ==Description== | ||
| + | |||
| + | A vulnerability is a weakness in an application (frequently a broken or missing control) that enables an attack to succeed. Be sure you don't put [attacks] or [controls] in this category. | ||
| + | |||
| + | # Start with a one-sentence description of the vulnerability | ||
| + | # What is the problem that creates the vulnerability? | ||
| + | # What are the attacks that target this vulnerability? | ||
| + | # What are the technical impacts of this vulnerability? | ||
| + | |||
"..\filename" | "..\filename" | ||
| − | |||
| − | ==Related | + | ==Risk Factors== |
| + | |||
| + | * Talk about the [[OWASP Risk Rating Methodology|factors]] that make this vulnerability likely or unlikely to actually happen | ||
| + | * Discuss the technical impact of a successful exploit of this vulnerability | ||
| + | * Consider the likely [business impacts] of a successful attack | ||
| + | |||
| + | |||
| + | ==Examples== | ||
| + | |||
| + | ===Short example name=== | ||
| + | : A short example description, small picture, or sample code with [http://www.site.com links] | ||
| + | |||
| + | ===Short example name=== | ||
| + | : A short example description, small picture, or sample code with [http://www.site.com links] | ||
| + | |||
| + | |||
| + | ==Related [[Attacks]]== | ||
| + | |||
| + | * [[Path Traversal]] | ||
| + | |||
| + | |||
| + | ==Related [[Vulnerabilities]]== | ||
| + | |||
| + | * [[Vulnerability 1]] | ||
| + | * [[Vulnerabiltiy 2]] | ||
| − | ==Related | + | ==Related [[Controls]]== |
| − | [ | + | * [[Control 1]] |
| + | * [[Control 2]] | ||
| − | |||
| − | ==Related | + | ==Related [[Technical Impacts]]== |
| − | + | * [[Technical Impact 1]] | |
| + | * [[Technical Impact 2]] | ||
| − | |||
| − | [[ | + | ==References== |
| + | Note: A reference to related [http://cwe.mitre.org/ CWE] or [http://capec.mitre.org/ CAPEC] article should be added when exists. Eg: | ||
| − | [[ | + | * [http://cwe.mitre.org/data/definitions/79.html CWE 79]. |
| + | * http://www.link1.com | ||
| + | * [http://www.link2.com Title for the link2] | ||
Latest revision as of 12:50, 3 June 2009
#REDIRECT Failure_to_follow_guideline/specification
Last revision (mm/dd/yy): 06/3/2009
Description
A vulnerability is a weakness in an application (frequently a broken or missing control) that enables an attack to succeed. Be sure you don't put [attacks] or [controls] in this category.
- Start with a one-sentence description of the vulnerability
- What is the problem that creates the vulnerability?
- What are the attacks that target this vulnerability?
- What are the technical impacts of this vulnerability?
"..\filename"
Risk Factors
- Talk about the factors that make this vulnerability likely or unlikely to actually happen
- Discuss the technical impact of a successful exploit of this vulnerability
- Consider the likely [business impacts] of a successful attack
Examples
Short example name
- A short example description, small picture, or sample code with links
Short example name
- A short example description, small picture, or sample code with links
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
Note: A reference to related CWE or CAPEC article should be added when exists. Eg:
