Impact
GLPIKEY is public and is used on every instance. This means anyone can decrypt sensitive data stored using this key.
Patches
efd1446 for GLPI 9.4
Workarounds
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't 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.
Reference
https://offsec.almond.consulting/multiple-vulnerabilities-in-glpi.html
Impact
GLPIKEY is public and is used on every instance. This means anyone can decrypt sensitive data stored using this key.
Patches
efd1446 for GLPI 9.4
Workarounds
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't 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.
Reference
https://offsec.almond.consulting/multiple-vulnerabilities-in-glpi.html