Software Error Category: Insecure Interaction Between Components

[1] CWE-79: Failure to Preserve Web Page Structure (‘Cross-site Scripting’)

Cross-site scripting (XSS) is one of the most prevalent, obstinate, and dangerous vulnerabilities in web applications…If you’re not careful, attackers can…MORE >>

[2] CWE-89: Failure to Preserve SQL Query Structure (aka ‘SQL Injection’)

If attackers can influence the SQL that you use to communicate with your database, then they can…MORE >>

[4] CWE-352: Cross-Site Request Forgery (CSRF)

With cross-site request forgery, the attacker gets the victim to activate a request that goes to your site. Thanks to scripting and the way the web works in general, the victim…MORE >>

[8] CWE-434: Unrestricted Upload of File with Dangerous Type

You may think you’re allowing uploads of innocent images…MORE >>

[9] CWE-78: Failure to Preserve OS Command Structure (aka ‘OS Command Injection’)

When you invoke another program on the operating system, but you allow untrusted inputs to be fed into the command string that you generate for executing the program, then you are inviting attackers…MORE >>

[17] CWE-209: Information Exposure Through an Error Message

If you use chatty error messages, then they could disclose secrets to any attacker who dares to misuse your software. The secrets could cover a wide range of valuable data…MORE >>

[23] CWE-601: URL Redirection to Untrusted Site (‘Open Redirect’)

While much of the power of the World Wide Web is in sharing and following links between web sites, typically there is…MORE >>

[25] CWE-362: Race Condition

Attackers will consciously look to exploit race conditions to cause chaos or get your application to cough up something valuable…MORE >>

Software Error Category: Risky Resource Management

[3] CWE-120: Buffer Copy without Checking Size of Input (‘Classic Buffer Overflow’)

Buffer overflows are Mother Nature’s little reminder of that law of physics that says if you try to put more stuff into a container than it can hold, you’re…MORE >>

[7] CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)

While data is often exchanged using files, sometimes you don’t intend to…MORE >>

[14] CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program (‘PHP File Inclusion’)

Not a lot of Top 25 weaknesses are unique to a single programming language, but that just goes to show how special this one is. The idea…MORE >>

[12] CWE-805: Buffer Access with Incorrect Length Value

A popular insult is: “Take a long walk off a short pier.” One programming equivalent for this… MORE >>

[13] CWE-754: Improper Check for Unusual or Exceptional Conditions

Security-wise, it pays to be cynical. If you always expect the worst…MORE >>


[15] CWE-129: Improper Validation of Array Index

If you’ve allocated an array of 100 objects or structures, and an attacker provides an index that is…MORE >>

[16] CWE-190: Integer Overflow or Wraparound

In the real world, 255+1=256. But to a computer program, sometimes 255+1=…MORE >>

[18] CWE-131: Incorrect Calculation of Buffer Size

In languages such as C, where memory management is the programmer’s responsibility, there are many opportunities for error…MORE >>

[20] CWE-494: Download of Code Without Integrity Check

You don’t need to be a guru to realize that if you download code and execute it, you’re trusting that the source of that code isn’t malicious. But attackers can perform all sorts of tricks…MORE >>

[21] CWE-770: Allocation of Resources Without Limits or Throttling

If someone calls in and places an order for a thousand pizzas (with anchovies) to be delivered immediately, you’d quickly put a stop to that nonsense. But…MORE >>

Software Error Category: Porous Defenses

[5] CWE-285: Improper Access Control (Authorization)

If you don’t ensure that your software’s users are only doing what they’re allowed to, then attackers will try to exploit your improper authorization and…MORE >>

[6] CWE-807: Reliance on Untrusted Inputs in a Security Decision

Driver’s licenses may require close scrutiny to identify fake licenses, or to determine if a person is using someone else’s license. Software developers…MORE >>

[10] CWE-311: Missing Encryption of Sensitive Data

If your software sends sensitive information across a network, such as private data or authentication credentials, that information…MORE >>

[11] CWE-798: Use of Hard-coded Credentials

Most of the CWE Top 25 can be explained away as an honest mistake; for this issue, though, customers…MORE >>

[19] CWE-306: Missing Authentication for Critical Function

In countless action movies, the villain breaks into a high-security building by crawling through heating ducts…MORE >>

[22] CWE-732: Incorrect Permission Assignment for Critical Resource

If you have critical programs, data stores, or configuration files with permissions that make your resources accessible to the world – well, that’s just what they’ll become…MORE >>

[24] CWE-327: Use of a Broken or Risky Cryptographic Algorithm

You may be tempted to develop your own encryption scheme in the hopes of making it difficult for attackers to crack. This kind of grow-your-own cryptography is a welcome sight to attackers…MORE >>