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.

Primary

Resultant

Architecture and Design

Implementation

This is an implementation error, in which the algorithm/technique requires certain security-related behaviors or conditions that are not implemented or checked properly, thus causing a vulnerability.

Access Control
Bypass Protection Mechanism

CVE-2002-0862
Browser does not verify Basic Constraints of a certificate, even though it is required, allowing spoofing of trusted certificates.
https://www.cve.org/CVERecord?id=CVE-2002-0862

CVE-2002-0970
Browser does not verify Basic Constraints of a certificate, even though it is required, allowing spoofing of trusted certificates.
https://www.cve.org/CVERecord?id=CVE-2002-0970

CVE-2002-1407
Browser does not verify Basic Constraints of a certificate, even though it is required, allowing spoofing of trusted certificates.
https://www.cve.org/CVERecord?id=CVE-2002-1407

CVE-2005-0198
Logic error prevents some required conditions from being enforced during Challenge-Response Authentication Mechanism with MD5 (CRAM-MD5).
https://www.cve.org/CVERecord?id=CVE-2005-0198

CVE-2004-2163
Shared secret not verified in a RADIUS response packet, allowing authentication bypass by spoofing server replies.
https://www.cve.org/CVERecord?id=CVE-2004-2163

CVE-2005-2181
Insufficient verification in VoIP implementation, in violation of standard, allows spoofed messages.
https://www.cve.org/CVERecord?id=CVE-2005-2181

CVE-2005-2182
Insufficient verification in VoIP implementation, in violation of standard, allows spoofed messages.
https://www.cve.org/CVERecord?id=CVE-2005-2182

CVE-2005-2298
Security check not applied to all components, allowing bypass.
https://www.cve.org/CVERecord?id=CVE-2005-2298

Improperly Implemented Security Check for Standard

Allowed
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

This is a "missing step" error on the product side, which can overlap weaknesses such as insufficient verification and spoofing. It is frequently found in cryptographic and authentication errors. It is sometimes resultant.

PLOVER
2006-07-19
Draft 3
2006-07-19

Eric Dalci
Cigital
2008-07-01
updated Time_of_Introduction

CWE Content Team
MITRE
2008-09-08
updated Relationships, Other_Notes, Taxonomy_Mappings

CWE Content Team
MITRE
2009-05-27
updated Description

CWE Content Team
MITRE
2009-10-29
updated Modes_of_Introduction, Observed_Examples, Other_Notes, Relationship_Notes

CWE Content Team
MITRE
2011-06-01
updated Common_Consequences, Relationships, Taxonomy_Mappings

CWE Content Team
MITRE
2012-05-11
updated Relationships, Taxonomy_Mappings

CWE Content Team
MITRE
2014-07-30
updated Relationships

CWE Content Team
MITRE
2015-12-07
updated Relationships

CWE Content Team
MITRE
2017-11-08
updated Applicable_Platforms

CWE Content Team
MITRE
2019-06-20
updated Relationships

CWE Content Team
MITRE
2020-02-24
updated Relationships

CWE Content Team
MITRE
2022-04-28
updated Relationships

CWE Content Team
MITRE
2023-01-31
updated Description

CWE Content Team
MITRE
2023-04-27
updated Relationships

CWE Content Team
MITRE
2023-06-29
updated Mapping_Notes

CWE Content Team
MITRE
2025-12-11
4.19
2025-12-11
updated Weakness_Ordinalities