Use this section to tell people about which versions of your project are currently being supported with security updates.

Use this section to tell people how to report a vulnerability.

Tell them where to go, how often they can expect to get an update on a reported vulnerability, what to expect if the vulnerability is accepted or declined, etc.

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 Attack 1 Attack 2 Related Vulnerabilities Vulnerability 1 Vulnerabiltiy 2 Note: the contents of “Related Problems” sections should be placed here

Related Controls Control 1 Control 2 Note: contents of “Avoidance and Mitigation” and “Countermeasure” related Sections should be placed here

Related Technical Impacts Technical Impact 1 Technical Impact 2 References Note: A reference to related CWE or CAPEC article should be added when exists. Eg:

CWE 79. http://www.link1.com Title for the link2 In addition, one should classify vulnerability based on the following subcategories: Ex:[[Category:Error_Handling_Vulnerability|Category:Error Handling Vulnerability]]