CWE-345: Insufficient Verification of Data Authenticity

Description

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

Extended Description

N/A

ThreatScore

Threat Mapped score: 0.0

Industry: Finiancial

Threat priority: Unclassified

Observed Examples (CVEs)

CVE: CVE-2022-30260

Distributed Control System (DCS) does not sign firmware images and only relies on insecure checksums for integrity checks
CVE: CVE-2022-30267

Distributed Control System (DCS) does not sign firmware images and only relies on insecure checksums for integrity checks
CVE: CVE-2022-30272

Remote Terminal Unit (RTU) does not use signatures for firmware images and relies on insecure checksums

Related Attack Patterns (CAPEC)

Attack TTPs

T1491 — Defacement (impact)
T1542.002 — Component Firmware (persistence, defense-evasion)
T1584.002 — DNS Server (resource-development)
T1557.002 — ARP Cache Poisoning (credential-access, collection)
T1556 — Modify Authentication Process (credential-access, defense-evasion, persistence)
T1211 — Exploitation for Defense Evasion (defense-evasion)

Malware

APTs (Intrusion Sets)

Modes of Introduction

Phase	Note
Architecture and Design	N/A
Implementation	REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Common Consequences

Impact: Varies by Context, Unexpected State — Notes:

Potential Mitigations

None listed.

Applicable Platforms

None (Not Language-Specific, Undetermined)

Demonstrative Examples

Intro: 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.

Body: Multiple vendors did not sign firmware images.

Notes

Relationship: "origin validation" could fall under this.
Maintenance: The specific ways in which the origin is not properly identified should be laid out as separate weaknesses. In some sense, this is more like a category.

← Back to CWE list