CWE-345: Insufficient Verification of Data Authenticity
Official CWE-345 CWE context with Glexia analysis, remediation guidance, related CVEs, and ATT&CK context.
Glexia's Take
CWE-345: Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Integrity,Other: Varies by Context,Unexpected State
Developer Pattern
CWE-345 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Confidence
high confidence from CWE-345, 4.20.
Official CWE Definition
CWE-345: Insufficient Verification of Data Authenticity
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications. Multiple vendors did not sign firmware images.
Remediation
- Use safe APIs
- Centralize the control
- Add regression tests
- Review logs and telemetry for attempted abuse
Detection
- Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
- CWE-1293: Missing Source Correlation of Multiple Independent Data
- CWE-1304: Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation
- CWE-20: Improper Input Validation
- CWE-693: Protection Mechanism Failure
- CWE-346: Origin Validation Error
- CWE-346: Origin Validation Error
- CWE-347: Improper Verification of Cryptographic Signature
- CWE-347: Improper Verification of Cryptographic Signature
- CWE-348: Use of Less Trusted Source
- CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data
- CWE-351: Insufficient Type Distinction
- CWE-352: Cross-Site Request Forgery (CSRF)
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.