CWE-351: Insufficient Type Distinction

BaseDraft

The product does not properly distinguish between different types of elements in a way that leads to insecure behavior.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-351: Insufficient Type Distinction?+

CWE-351: Insufficient Type Distinction is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not properly distinguish between different types of elements in a way that leads to insecure behavior.

What are the security consequences of Insufficient Type Distinction?+

If exploited, CWE-351 (Insufficient Type Distinction) it can compromise Other, leading to outcomes such as Other.

Which programming languages are affected by Insufficient Type Distinction?+

CWE-351 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Insufficient Type Distinction?+

MITRE documents real CVEs mapped to CWE-351, including CVE-2005-2260 and CVE-2005-2801. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-351 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

CWE-351: Insufficient Type Distinction | CWE Lookup | InventiveHQ