CVE-2020-5248
Summary
| CVE | CVE-2020-5248 |
|---|
| State | PUBLIC |
|---|
| Assigner | [email protected] |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2020-05-12 16:15:00 UTC |
|---|
| Updated | 2020-05-14 17:08:00 UTC |
|---|
| 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. |
|---|
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|
| Deprecate GLPIKEY usage · glpi-project/glpi@efd1446 · GitHub |
MISC |
github.com |
Patch, Third Party Advisory |
| Public GLPIKEY can be used to decrypt any data · Advisory · glpi-project/glpi · GitHub |
CONFIRM |
github.com |
Mitigation, Third Party Advisory |
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
Legacy QID Mappings
- 690671 Free Berkeley Software Distribution (FreeBSD) Security Update for glpi (b3695b08-3b3a-11eb-af2a-080027dbe4b7)
