{"id":20758,"date":"2024-05-02T13:47:28","date_gmt":"2024-05-02T20:47:28","guid":{"rendered":"https:\/\/webdev.securin.xyz\/?p=20758"},"modified":"2024-05-03T08:31:31","modified_gmt":"2024-05-03T15:31:31","slug":"common-weakness-enumeration-cwes-context-is-everything","status":"publish","type":"post","link":"https:\/\/webdev.securin.xyz\/articles\/common-weakness-enumeration-cwes-context-is-everything","title":{"rendered":"Common Weakness Enumeration (CWEs): Context is Everything"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

You are the weakest link. Hello. <\/strong><\/p>

\u201cWhen you hear the sound of hooves, think horses, not zebras\u201d is something many doctors are taught at medical school. Essentially, it means that, when you\u2019re thinking about a diagnosis, consider the most likely possibility first. But not all diseases are horses, sometimes there\u2019s a zebra in there, making trouble.\u00a0<\/span><\/p>

What does any of this have to do with weakness in code and vulnerability management?\u00a0<\/span><\/p>

Well, just like in medicine, there are times when, if you only look at the main symptoms, you\u2019ll miss the disease. And if you focus your priorities and efforts completely on the MITRE Top 25<\/a>, there\u2019s a good chance you\u2019ll miss the highly weaponized, less known weakness that is highly relevant to <\/span>your specific systems<\/span><\/i>. Until it finds you.\u00a0<\/span><\/p>

So what are these weaknesses and why should developers and defenders focus on them?<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t

Understanding is the Key \n<\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

Common Weakness Enumerations (CWEs)<\/a> are weaknesses or inherent flaws in software design, implementation or operation that can be exploited by attackers. They\u2019re the foundation for vulnerabilities (CVEs) within software systems, where a vulnerability is a specific instance of a weakness that can be exploited.\u00a0<\/span><\/p>

Understanding the nature of weakness is crucial for developing a proactive cybersecurity approach. Organizations that understand the root causes behind weaponized and exploited vulnerabilities can prioritize efforts to identify, mitigate and remediate weakness – <\/span>before<\/span><\/i> they are leveraged by attackers and become known as exploited vulnerabilities. This proactive approach helps minimize the risk of potential exploits, enhancing the overall security posture of software systems.\u00a0<\/span><\/p>

What kind of insights can we gain from this approach?\u00a0<\/span><\/p>

Securin\u2019s analysts tracked 311,018 CVEs<\/strong> that, as of April 9 2024, have CWEs assigned to them. Here\u2019s what we found:<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

Key Notes:<\/span><\/strong><\/p>