Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Glpi-Project | Glpi | < 9.4.6 |
Related Weaknesses (CWE)
References
- https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbcPatchThird Party Advisory
- https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9MitigationThird Party Advisory
- https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbcPatchThird Party Advisory
- https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9MitigationThird Party Advisory
FAQ
What is CVE-2020-5248?
CVE-2020-5248 is a vulnerability with a CVSS score of 7.2 (HIGH). 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...
How severe is CVE-2020-5248?
CVE-2020-5248 has been rated HIGH with a CVSS base score of 7.2/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-5248?
Check the references section above for vendor advisories and patch information. Affected products include: Glpi-Project Glpi.