DerScanner
Home / Vulnerability Database / C or C++ : Hardcoded initialization vector
C/C++

C or C++ : Hardcoded initialization vector

Classification

OWASP Top 10 2013
A6-Sensitive Data Exposure
OWASP Top 10 2017
A3-Sensitive Data Exposure
OWASP Top 10 2021
A2-Cryptographic FailuresA4-Insecure Design
OWASP MASVS
V8: 8.13.(L1+R/L2+R)
OWASP ASVS
Stored CryptographyStored CryptographyAuthentication
PCI DSS 4.0
3.6.16.2.48.3.2
HIPAA
§164.312 (a)(2)(iv)
CWE
CWE-257CWE-329CWE-522CWE-798CWE-1032
CWE/SANS Top 25 2011
CWE-798
CWE/SANS Top 25 2021
CWE-522CWE-798

Overview

The application performs encryption with hardcoded initialization vector (IV). In case of encrypting related messages with the same key and hardcoded IV an attacker can obtain information about the message. For secure encryption it is necessary for the IV to be cryptographically pseudorandom, that is, unpredictable to an attacker.

Sensitive Data Exposure vulnerabilities take the third place in the “OWASP Top 10 2017” web-application vulnerabilities ranking.

References

  1. CWE-329: Not Using a Random IV with CBC Mode
  2. Initialization vector - Wikipedia
  3. Forced into using a static IV (AES) - security.stackexchange.com
  4. Why should I use an Initialization Vector (IV) when I have unique keys? - crypto.stackexchange.com
  5. OWASP Top 10 2017-A3-Sensitive Data Exposure
  6. CWE CATEGORY: OWASP Top Ten 2017 Category A6 - Security Misconfiguration
  7. CWE-798: Use of Hard-coded Credentials
MEDIUM

DerScanner Severity Score

Do you want to fix C or C++ : Hardcoded initialization vector in your application?

See also

C/C++

C or C++ : Dead store

C/C++

C or C++ : Use after free

C/C++

C or C++ : va_list uninitialized