CVE-2017-5999
Last modified
CVE-2017-5999 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.14% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Syspass | Syspass | 2.0 |
References
- http://www.securityfocus.com/bid/96562Third Party Advisory, VDB Entry
- https://cxsecurity.com/issue/WLB-2017020196Third Party Advisory
- https://github.com/nuxsmin/sysPass/releases/tag/2.1.0.17022601Patch, Release Notes
- http://www.securityfocus.com/bid/96562Third Party Advisory, VDB Entry
- https://cxsecurity.com/issue/WLB-2017020196Third Party Advisory
- https://github.com/nuxsmin/sysPass/releases/tag/2.1.0.17022601Patch, Release Notes
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5999?
How severe is CVE-2017-5999?
How do I fix CVE-2017-5999?
Are you affected by CVE-2017-5999?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
