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 "J2EE Bad Practices: Threads"
From OWASP
(Reverting to last version not containing links to www.textdelsitlitav.com) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{template:CandidateForDeletion}} | {{template:CandidateForDeletion}} | ||
| − | + | #REDIRECT [[Failure to follow guideline/specification]] | |
| − | |||
| − | [[ | ||
Latest revision as of 18:27, 27 May 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 05/27/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?
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:
