CVE-2017-5999
Syspass vulnerability
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.
Affected products
Syspass. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Syspass runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/nuxsmin/sysPass/commit/a0e2c485e53b370a7cc6d833e192c3c5bfd70e1f · Patch
- github.com/nuxsmin/sysPass/releases/tag/2.1.0.17022601 · Patch
- www.securityfocus.com/bid/96562 · Third Party Advisory
- cxsecurity.com/issue/WLB-2017020196 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2017-5999
- cve.org/CVERecord?id=CVE-2017-5999
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.