Vulnerability in Glpi-Project Glpi
CVE-2020-11031
In GLPI before version 9.5.0, the encryption algorithm used is insecure. The security of the data encrypted relies on the password used, if a user sets a weak/predictable password, an attacker could decrypt data. This is fixed in version 9.5.0 by using a more secure encryption library. The library chosen is sodium.
Vulnerability class: POODLE (CVE-2014-3566)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N.
EPSS exploit prediction
EPSS: 0.003 (23.3th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 23rd percentile — 23.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.003 · change: 0.000
Affected products
- Glpi-Project Glpi — versions < 9.5.0
Weakness classification (CWE)
References
- github.com/glpi-project/glpi/security/advisories/GHSA-7xwm-4vjr-jvqh (Third Party Advisory)
- github.com/glpi-project/glpi/commit/f1ae6c8481e5c19a6f1801a5548cada45702e01a (Patch, Third Party Advisory)
Frequently asked questions
- What is CVE-2020-11031?
- CVE-2020-11031 is a high-severity vulnerability in Glpi-Project Glpi, classified under Use of a Broken or Risky Cryptographic Algorithm. CVSS score: 7.8/10. Published 2020-09-23.
- How severe is CVE-2020-11031?
- High severity. CVSS v3 base score is 7.8 out of 10.