CWE

• Get CWE versionGet the version of the CWE catalogue MITRE is publishing, the day it was released, and how many weaknesses, categories and views it holds. Run it on a schedule to notice a new release. No API key required.
• Look up CWE entriesTurn one or more CWE ids, such as those in a scanner report or a CVE record, into their names, what each is (a weakness, a category or a view), how specific it is, its status and its description. Ids CWE does not have come back marked as not found rather than failing the step. No API key required.
• Search weaknessesFind weaknesses by words in their name, other names or description (such as 'sql injection' or 'deserialization'), by a CVE id they list as an example, or by how general they are, how likely they are to be exploited, whether CWE wants them used for vulnerability mapping, and when they last changed. Leave everything empty to list every weakness. No API key required.
• Get weaknessRead one weakness in full: its description, how likely it is to be exploited, what an attacker can do through it, how to prevent it and find it, the languages and technologies it affects, the real vulnerabilities (CVE ids) it has caused, worked code examples, related weaknesses and attack patterns, and whether CWE wants it used to name a vulnerability's root cause. No API key required.
• Search categoriesFind categories, the groups CWE files weaknesses under, by words in their name or summary: an OWASP Top Ten entry such as 'A03:2021', a coding standard's rules, or a topic such as 'cryptographic'. Leave the words empty to list every category. No API key required.
• Get categoryRead one category: its summary, the view it belongs to, and every weakness it groups, each named. Use it to list the weaknesses behind an OWASP Top Ten entry or a topic such as Numeric Errors. No API key required.
• List viewsList every view, the ways CWE arranges its weaknesses for one audience or purpose: the yearly Top 25 lists, the OWASP Top Ten, the views for software developers, hardware designers and researchers, and the views for each coding standard. No API key required.
• Get viewRead one view: what it is for, who it is for, and its members in the view's own order, each named. Pick a Top 25 view to get the Top 25 in rank order. No API key required.
• Get parentsGet the entries directly above a weakness, category or view: the more general weakness or the category it sits under, in one view or every view, each named and marked when it is the primary parent. Searching every view also lists the views that include it directly, such as a Top 25. No API key required.
• Get childrenGet the entries directly under a weakness, category or view in one view, in that view's order, each named: the more specific weaknesses under a weakness, the weaknesses in a category, or the top level of a view (a Top 25 in rank order). No API key required.
• Get ancestorsGet everything above a weakness, category or view, up to the top of the view, each named with how many levels up it is, plus each route up written out (such as CWE-79 > CWE-74 > CWE-707 > CWE-1000). Use it to roll a specific weakness up to its broad class for reporting. No API key required.
• Get descendantsGet everything below a weakness, category or view in one view, level by level, each named with how deep it is and what it sits under. Use it to list every specific weakness that counts as, say, injection (CWE-74), or every weakness in a view. No API key required.

No actions match that.