Vulnerability Details : CVE-2017-5999
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.
Exploit prediction scoring system (EPSS) score for CVE-2017-5999
Probability of exploitation activity in the next 30 days: 0.22%
Percentile, the proportion of vulnerabilities that are scored at or less: ~ 60 % EPSS Score History EPSS FAQ
CVSS scores for CVE-2017-5999
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source |
---|---|---|---|---|---|
5.0
|
MEDIUM | AV:N/AC:L/Au:N/C:P/I:N/A:N |
10.0
|
2.9
|
NIST |
7.5
|
HIGH | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
3.9
|
3.6
|
NIST |
CWE ids for CVE-2017-5999
-
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.Assigned by: nvd@nist.gov (Primary)
References for CVE-2017-5999
-
http://www.securityfocus.com/bid/96562
sysPass CVE-2017-5999 Cryptographic Security Bypass VulnerabilityThird Party Advisory;VDB Entry
-
https://github.com/nuxsmin/sysPass/releases/tag/2.1.0.17022601
Release sysPass 2.1 · nuxsmin/sysPass · GitHubPatch;Release Notes
-
https://cxsecurity.com/issue/WLB-2017020196
sysPass 2.0 risky cryptographic algorithm usage - CXSecurity.comThird Party Advisory
-
https://github.com/nuxsmin/sysPass/commit/a0e2c485e53b370a7cc6d833e192c3c5bfd70e1f
Merge branch 'crypt' · nuxsmin/sysPass@a0e2c48 · GitHubPatch
Products affected by CVE-2017-5999
- cpe:2.3:a:syspass:syspass:2.0:*:*:*:*:*:*:*