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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: GitHub_M
Published: 2020-05-12T16:05:17
Updated: 2024-08-04T08:22:09.092Z
Reserved: 2020-01-02T00:00:00
Link: CVE-2020-5248
Vulnrichment
No data.
NVD
Status : Modified
Published: 2020-05-12T16:15:11.157
Modified: 2024-11-21T05:33:45.710
Link: CVE-2020-5248
Redhat
No data.