Vulnerability in Glpi-Project Glpi
CVE-2020-5248
GLPI before before version 9.4.6 has a vulnerability involving a default encryption key. GLPIKEY is public and is used on every instance. This means anyone can decrypt sensitive data stored using this key. It is possible to change the key before installing GLPI. But on existing instances, data must be reencrypted with the new key. Problem is we can not know which columns or rows in the database are using that; espcially from plugins. Changing the key without updating data would lend in bad password sent from glpi; but storing them again from the UI will work.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.2 (High). Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N.
EPSS exploit prediction
EPSS: 0.015 (73.8th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 74th percentile — 73.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.015 · newest: 0.015 · change: 0.000
Affected products
- Glpi-Project Glpi — versions < 9.4.6
Weakness classification (CWE)
Public proof-of-concept exploits
References
- github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9 (Third Party Advisory, Mitigation)
- github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c (Patch, Third Party Advisory)
Frequently asked questions
- What is CVE-2020-5248?
- CVE-2020-5248 is a high-severity vulnerability in Glpi-Project Glpi, classified under Use of Hard-coded Credentials. CVSS score: 7.2/10. Published 2020-05-12.
- How severe is CVE-2020-5248?
- High severity. CVSS v3 base score is 7.2 out of 10.
- Is CVE-2020-5248 known to be exploited?
- 11 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.