Home / Vulnerability Database / Kotlin : Insecure initialization vector
Kotlin
Kotlin : Insecure initialization vector
Classification
OWASP Top 10 2013
OWASP Top 10 2017
OWASP Top 10 2021
OWASP MASVS
OWASP ASVS
HIPAA
Overview
The application performs encryption with the initialization vector (IV) and coincides encryption keys. For secure encryption it is necessary that IV be cryptographically pseudo-random, that is unpredictable for the attacker.
Sensitive Data Exposure vulnerabilities take the third place in the “OWASP Top 10 2017” web-application vulnerabilities ranking.
References
- CWE-329: Not Using a Random IV with CBC Mode
- Initialization vector - Wikipedia
- Forced into using a static IV (AES) - security.stackexchange.com
- Why should I use an Initialization Vector (IV) when I have unique keys? - crypto.stackexchange.com
- OWASP Top 10 2017-A3-Sensitive Data Exposure
- CWE CATEGORY: OWASP Top Ten 2017 Category A6 - Security Misconfiguration
- Bleichenbacher’s attack
MEDIUM
DerScanner Severity Score
Do you want to fix Kotlin : Insecure initialization vector in your application?
See also
Kotlin
Kotlin : Missing required cryptographic step
Kotlin
Kotlin : Logging into system output
Kotlin
