CVEvulnerability

CVE-2020-5248

5.3 MEDIUM Published 2020-05-12 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2020-05-12
Last modified
2026-06-17
Assigner
[email protected]
CVSS 3.1 ([email protected])
7.2 HIGH — CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
CVSS 3.1 ([email protected])
5.3 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS 2.0 ([email protected])
5.0 MEDIUM — AV:N/AC:L/Au:N/C:P/I:N/A:N
Weaknesses
CWE-798

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.

Affected configurations

• glpi-project glpi (< 9.4.6)

Related

Weakness · CWE (1)

  • CWE-798 Use of Hard-coded Credentials weakness

Referenced by CWE · observed example (1)

  • CWE-1391 Use of Weak Credentials weakness

References