← Back to CVEs

CVE-2020-5248

HIGH

7.2

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.

CVE Details

CVSS v3.1 Score7.2

SeverityHIGH

CVSS VectorCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N

Attack VectorLOCAL

ComplexityHIGH

Privileges RequiredHIGH

User InteractionNONE

Published5/12/2020

Last Modified11/21/2024

Sourcenvd

Honeypot Sightings0

Affected Products

glpi-project:glpi

Weaknesses (CWE)

CWE-798CWE-798

References

https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c(security-advisories@github.com)

https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9(security-advisories@github.com)

https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c(af854a3a-2127-422b-91ae-364da2661108)

https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9(af854a3a-2127-422b-91ae-364da2661108)

IOC Correlations

No correlations recorded

This product uses data from the NVD API but is not endorsed or certified by the NVD.