- Home
-
CWE-345: Insufficient Verification of Data Authenticity
Weakness ID: 345Vulnerability Mapping: DISCOURAGED This CWE ID should not be used to map to real-world vulnerabilities
Abstraction: Class Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource.View customized information:For users who are interested in more notional aspects of a weakness. Example: educators, technical writers, and project/program managers. For users who are concerned with the practical application and details about the nature of a weakness and how to prevent it from happening. Example: tool developers, security researchers, pen-testers, incident response analysts. For users who are mapping an issue to CWE/CAPEC IDs, i.e., finding the most appropriate CWE for a specific issue (e.g., a CVE record). Example: tool developers, security researchers. For users who wish to see all available information for the CWE/CAPEC entry. For users who want to customize what details are displayed.
Description
Common Consequences
This table specifies different individual consequences
associated with the weakness. The Scope identifies the application security area that is
violated, while the Impact describes the negative technical impact that arises if an
adversary succeeds in exploiting this weakness. The Likelihood provides information about
how likely the specific consequence is expected to be seen relative to the other
consequences in the list. For example, there may be high likelihood that a weakness will be
exploited to achieve a certain impact, but a low likelihood that it will be exploited to
achieve a different impact.
Impact Details Varies by Context; Unexpected State
Scope: Integrity, Other
Relationships
This table shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOf and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition,
relationships such as PeerOf and CanAlsoBe are defined to show similar weaknesses that the user
may want to explore.
Relevant to the view "Research Concepts" (View-1000)
Nature Type ID Name ChildOf 
Pillar - a weakness that is the most abstract type of weakness and represents a theme for all class/base/variant weaknesses related to it. A Pillar is different from a Category as a Pillar is still technically a type of weakness that describes a mistake, while a Category represents a common characteristic used to group related things.
693 Protection Mechanism Failure ParentOf 
Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource.
346 Origin Validation Error ParentOf 
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
347 Improper Verification of Cryptographic Signature ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
348 Use of Less Trusted Source ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
349 Acceptance of Extraneous Untrusted Data With Trusted Data ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
351 Insufficient Type Distinction ParentOf 
Composite - a Compound Element that consists of two or more distinct weaknesses, in which all weaknesses must be present at the same time in order for a potential vulnerability to arise. Removing any of the weaknesses eliminates or sharply reduces the risk. One weakness, X, can be "broken down" into component weaknesses Y and Z. There can be cases in which one weakness might not be essential to a composite, but changes the nature of the composite when it becomes a vulnerability.
352 Cross-Site Request Forgery (CSRF) ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
353 Missing Support for Integrity Check ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
354 Improper Validation of Integrity Check Value ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
360 Trust of System Event Data ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
494 Download of Code Without Integrity Check ParentOf 
Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.
616 Incomplete Identification of Uploaded File Variables (PHP) ParentOf
Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.
646 Reliance on File Name or Extension of Externally-Supplied File ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
649 Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
924 Improper Enforcement of Message Integrity During Transmission in a Communication Channel ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
1293 Missing Source Correlation of Multiple Independent Data PeerOf
Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource.
20 Improper Input Validation PeerOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
1304 Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation
Relevant to the view "Weaknesses for Simplified Mapping of Published Vulnerabilities" (View-1003)
Nature Type ID Name MemberOf 
View - a subset of CWE entries that provides a way of examining CWE content. The two main view structures are Slices (flat lists) and Graphs (containing relationships between entries).
1003 Weaknesses for Simplified Mapping of Published Vulnerabilities ParentOf
Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource.
346 Origin Validation Error ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
347 Improper Verification of Cryptographic Signature ParentOf
Composite - a Compound Element that consists of two or more distinct weaknesses, in which all weaknesses must be present at the same time in order for a potential vulnerability to arise. Removing any of the weaknesses eliminates or sharply reduces the risk. One weakness, X, can be "broken down" into component weaknesses Y and Z. There can be cases in which one weakness might not be essential to a composite, but changes the nature of the composite when it becomes a vulnerability.
352 Cross-Site Request Forgery (CSRF) ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
354 Improper Validation of Integrity Check Value ParentOf
Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.
924 Improper Enforcement of Message Integrity During Transmission in a Communication Channel
Relevant to the view "Architectural Concepts" (View-1008)
Nature Type ID Name MemberOf 
Category - a CWE entry that contains a set of other entries that share a common characteristic.
1014 Identify Actors
Modes
Of IntroductionThe different Modes of Introduction provide information
about how and when this
weakness may be introduced. The Phase identifies a point in the life cycle at which
introduction
may occur, while the Note provides a typical scenario related to introduction during the
given
phase.
Phase Note Architecture and Design Implementation REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Applicable PlatformsThis listing shows possible areas for which the given
weakness could appear. These
may be for specific named Languages, Operating Systems, Architectures, Paradigms,
Technologies,
or a class of such platforms. The platform is listed along with how frequently the given
weakness appears for that instance.
Languages Class: Not Language-Specific (Undetermined Prevalence)
Technologies Class: ICS/OT (Undetermined Prevalence)
Demonstrative Examples Selected Observed
Examples
Weakness Ordinalities Detection
Methods Memberships
This MemberOf Relationships table shows additional CWE Categories and Views that
reference this weakness as a member. This information is often useful in understanding where a
weakness fits within the context of external information sources.
Nature Type ID Name MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic.724 OWASP Top Ten 2004 Category A3 - Broken Authentication and Session Management MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic.949 SFP Secondary Cluster: Faulty Endpoint Authentication MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic.1354 OWASP Top Ten 2021 Category A08:2021 - Software and Data Integrity Failures MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic.1411 Comprehensive Categorization: Insufficient Verification of Data Authenticity MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic.1443 OWASP Top Ten 2025 Category A08:2025 - Software or Data Integrity Failures
Vulnerability Mapping Notes Notes Taxonomy
Mappings
Related Attack Patterns References Content
History SubmissionsSubmission Date Submitter Organization 2006-07-19
(CWE Draft 3, 2006-07-19)PLOVER 
ModificationsModification Date Modifier Organization 2025-12-11
(CWE 4.19, 2025-12-11)CWE Content Team MITRE updated Relationships, Weakness_Ordinalities 2024-02-29
(CWE 4.14, 2024-02-29)CWE Content Team MITRE updated Mapping_Notes 2023-06-29 CWE Content Team MITRE updated Mapping_Notes 2023-04-27 CWE Content Team MITRE updated Detection_Factors, Relationships 2023-01-31 CWE Content Team MITRE updated Applicable_Platforms, Demonstrative_Examples, Description, Observed_Examples, References, Related_Attack_Patterns 2021-10-28 CWE Content Team MITRE updated Relationships 2021-07-20 CWE Content Team MITRE updated Related_Attack_Patterns 2020-08-20 CWE Content Team MITRE updated Relationships 2020-06-25 CWE Content Team MITRE updated Relationships 2020-02-24 CWE Content Team MITRE updated Relationships 2019-06-20 CWE Content Team MITRE updated Related_Attack_Patterns, Relationships 2017-11-08 CWE Content Team MITRE updated Applicable_Platforms, Modes_of_Introduction, Relationships 2017-05-03 CWE Content Team MITRE updated Related_Attack_Patterns 2015-12-07 CWE Content Team MITRE updated Relationships 2014-07-30 CWE Content Team MITRE updated Relationships 2013-07-17 CWE Content Team MITRE updated Relationships 2012-05-11 CWE Content Team MITRE updated References, Related_Attack_Patterns, Relationships 2011-06-27 CWE Content Team MITRE updated Common_Consequences 2011-06-01 CWE Content Team MITRE updated Common_Consequences 2010-12-13 CWE Content Team MITRE updated Related_Attack_Patterns 2010-04-05 CWE Content Team MITRE updated Related_Attack_Patterns 2010-02-16 CWE Content Team MITRE updated Taxonomy_Mappings 2009-07-27 CWE Content Team MITRE updated Related_Attack_Patterns 2009-05-27 CWE Content Team MITRE updated Related_Attack_Patterns 2008-09-08 CWE Content Team MITRE updated Maintenance_Notes, Relationships, Relationship_Notes, Taxonomy_Mappings 2008-07-01 Eric Dalci Cigital updated Time_of_Introduction Previous Entry NamesChange Date Previous Entry Name 2008-04-11 Insufficient Verification of Data
