Difference between revisions of "URL Encoding (Hex Encoding)"
From OWASP
Weilin Zhong (talk | contribs) |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{template:CandidateForDeletion}} |
| + | |||
| + | |||
| + | #REDIRECT [[::Category:Vulnerability]] | ||
| + | |||
| + | |||
| + | 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? | ||
The product does not properly handle when all or part of an input has been URL encoded. | The product does not properly handle when all or part of an input has been URL encoded. | ||
| Line 7: | Line 22: | ||
PLOVER - URL Encoding (Hex Encoding) | PLOVER - URL Encoding (Hex Encoding) | ||
| − | |||
| − | |||
| − | ==Related Attacks== | + | ==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]]== | ||
| + | |||
| + | * [[Attack 1]] | ||
| + | * [[Attack 2]] | ||
| + | |||
| + | |||
| + | ==Related [[Vulnerabilities]]== | ||
| + | |||
| + | * [[Vulnerability 1]] | ||
| + | * [[Vulnerabiltiy 2]] | ||
| + | |||
| + | |||
| + | |||
| + | ==Related [[Controls]]== | ||
| + | |||
| + | * [[:Category:Encoding]] | ||
| + | |||
| − | ==Related | + | ==Related [[Technical Impacts]]== |
| − | + | * [[Technical Impact 1]] | |
| − | [[ | + | * [[Technical Impact 2]] |
| − | |||
| − | + | ==References== | |
| − | + | TBD | |
Latest revision as of 01:08, 15 April 2009
#REDIRECT :Category:Vulnerability
Last revision (mm/dd/yy): 04/15/2009
Contents
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?
The product does not properly handle when all or part of an input has been URL encoded.
PLOVER - URL Encoding (Hex Encoding)
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
TBD
