CVE-2020-5248

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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:glpi-project:glpi:*:*:*:*:*:*:*:*

History

21 Nov 2024, 05:33

Type Values Removed Values Added
References () https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c - Patch, Third Party Advisory () https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c - Patch, Third Party Advisory
References () https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9 - Mitigation, Third Party Advisory () https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9 - Mitigation, Third Party Advisory
CVSS v2 : 5.0
v3 : 5.3
v2 : 5.0
v3 : 7.2

Information

Published : 2020-05-12 16:15

Updated : 2024-11-21 05:33


NVD link : CVE-2020-5248

Mitre link : CVE-2020-5248

CVE.ORG link : CVE-2020-5248


JSON object : View

Products Affected

glpi-project

  • glpi
CWE
CWE-798

Use of Hard-coded Credentials