CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2020 · Glpi-project

CVE-2020-5248
Glpi-project Glpi vulnerability

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.

Affected products

Glpi. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Glpi-project Glpi runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Set the orderSystems that can be reached from the internet come first, then the rest.

References

More vulnerabilities in Glpi-project products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.