CWE-358: Improperly Implemented Security Check for Standard

BaseDraft

The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-358: Improperly Implemented Security Check for Standard?+

CWE-358: Improperly Implemented Security Check for Standard is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.

What are the security consequences of Improperly Implemented Security Check for Standard?+

If exploited, CWE-358 (Improperly Implemented Security Check for Standard) it can compromise Access Control, leading to outcomes such as Bypass Protection Mechanism.

Which programming languages are affected by Improperly Implemented Security Check for Standard?+

CWE-358 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 Improperly Implemented Security Check for Standard?+

MITRE documents real CVEs mapped to CWE-358, including CVE-2002-0862, CVE-2002-0970, CVE-2002-1407, CVE-2005-0198 and CVE-2004-2163. 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-358 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