CVE-2020-5248
Public GLPIKEY can be used to decrypt any data in GLPI
Reported by github_m · Published May 12, 2020
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.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| glpi-project | glpi | < 9.4.6 |
| glpi-project | glpi | 0 |
Timeline
- May 12, 2020 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Aug 4, 2024 CVE Updated
- Aug 30, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2020-5248
vulnetix vdb fixes CVE-2020-5248
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-5248/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart