CWE-347: Improper Verification of Cryptographic Signature

Export to Word

Description

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

Extended Description

N/A

ThreatScore

Threat Mapped score: 0.0

Industry: Finiancial

Threat priority: Unclassified

Observed Examples (CVEs)

CVE: CVE-2002-1796

Does not properly verify signatures for "trusted" entities.
CVE: CVE-2005-2181

Insufficient verification allows spoofing.
CVE: CVE-2005-2182

Insufficient verification allows spoofing.
CVE: CVE-2002-1706

Accepts a configuration file without a Message Integrity Check (MIC) signature.

Related Attack Patterns (CAPEC)

Attack TTPs

N/A

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: Gain Privileges or Assume Identity, Modify Application Data, Execute Unauthorized Code or Commands — Notes: An attacker could gain access to sensitive data and possibly execute unauthorized code.

Potential Mitigations

None listed.

Applicable Platforms

None (Not Language-Specific, Undetermined)

Demonstrative Examples

Intro: In the following code, a JarFile object is created from a downloaded file.

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

File f = new File(downloadedFilePath); JarFile jf = new JarFile(f);

Notes

No notes available.

← Back to CWE list