CVE-2020-5248

High

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.

SeverityHigh
CVSS7.2
Exploit probability—
ProductGlpi
PublishedMay 12, 2020
First seenMay 12, 2020

How to fix

Update
  • glpi-project glpi9.4.6 or later

Affected products

ProductAffected versionsFixed in
glpi-project glpiv < 9.4.69.4.6

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.