The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
View on MITRENo mitigation information available for this CWE.
No detection method information available for this CWE.
Distributed Control System (DCS) does not sign firmware images and only relies on insecure checksums for integrity checks
View DetailsDistributed Control System (DCS) does not sign firmware images and only relies on insecure checksums for integrity checks
View DetailsRemote Terminal Unit (RTU) does not use signatures for firmware images and relies on insecure checksums
View DetailsNo relationship information available for this CWE.
CWE-345: Insufficient Verification of Data Authenticity is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
If exploited, CWE-345 (Insufficient Verification of Data Authenticity) it can compromise Integrity and Other, leading to outcomes such as Varies by Context and Unexpected State.
CWE-345 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
MITRE documents real CVEs mapped to CWE-345, including CVE-2022-30260, CVE-2022-30267 and CVE-2022-30272. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
A CWE (Common Weakness Enumeration) like CWE-345 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.