An issue was discovered in sysPass 2.x before 2.1, in which an algorithm was never sufficiently reviewed by cryptographers. The fact that inc/SP/Core/Crypt.class is using the MCRYPT_RIJNDAEL_256() function (the 256-bit block version of Rijndael, not AES) instead of MCRYPT_RIJNDAEL_128 (real AES) could help an attacker to create unknown havoc in the remote system.
References
Link | Resource |
---|---|
https://github.com/nuxsmin/sysPass/releases/tag/2.1.0.17022601 | Patch Release Notes |
https://github.com/nuxsmin/sysPass/commit/a0e2c485e53b370a7cc6d833e192c3c5bfd70e1f | Patch |
https://cxsecurity.com/issue/WLB-2017020196 | Third Party Advisory |
http://www.securityfocus.com/bid/96562 | Third Party Advisory VDB Entry |
Configurations
Information
Published : 2017-03-05 22:59
Updated : 2017-03-15 11:42
NVD link : CVE-2017-5999
Mitre link : CVE-2017-5999
JSON object : View
CWE
CWE-326
Inadequate Encryption Strength
Products Affected
syspass
- syspass