The product does not verify, or incorrectly verifies, the cryptographic signature for data.
View on MITREAn attacker could gain access to sensitive data and possibly execute unauthorized code.
No mitigation information available for this CWE.
No detection method information available for this CWE.
In the following code, a JarFile object is created from a downloaded file.
The JAR file that was potentially downloaded from an untrusted source is created without verifying the signature (if present). An alternate constructor that accepts a boolean verify parameter should be used instead.
Accepts a configuration file without a Message Integrity Check (MIC) signature.
View DetailsCWE-347: Improper Verification of Cryptographic Signature is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not verify, or incorrectly verifies, the cryptographic signature for data.
If exploited, CWE-347 (Improper Verification of Cryptographic Signature) it can compromise Access Control, Integrity and Confidentiality, leading to outcomes such as Gain Privileges or Assume Identity, Modify Application Data and Execute Unauthorized Code or Commands.
CWE-347 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-347, including CVE-2002-1796, CVE-2005-2181, CVE-2005-2182 and CVE-2002-1706. 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-347 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.