CVE-2020-5248 Public GLPIKEY can be used to decrypt any data in GLPI
Attackers can decrypt sensitive data in GLPI instances because the application uses a public, hardcoded encryption key by default.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2020-5248?
CVE-2020-5248 is a high-severity vulnerability in Glpi-Project Glpi, published on 12 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Weakness: CWE-798
Which versions are affected by CVE-2020-5248?
It affects 1 product.
Products include Glpi-Project Glpi.
How do I fix CVE-2020-5248?
No fix has been published for CVE-2020-5248 yet. Limit exposure of the affected software until one is available.
Is CVE-2020-5248 being exploited?
There is no known exploitation of CVE-2020-5248 in the wild and no public exploit code.
Public exploit code: 2 proofs of concept on GitHub.
Other vulnerabilities in Glpi-Project Glpi
- CVE-2022-35914 Teclib GLPI Remote Code Execution
- CVE-2023-42802 GLPI vulnerable to unallowed PHP script execution
- CVE-2023-28849 GLPI vulnerable to SQL injection and Stored XSS via inventory agent request
- CVE-2022-35947 SQL injection in GLPI
- CVE-2022-31056 SQL injection with _actor parameter in GLPI
Sources
Also known as GHSA-j222-j9mf-h6j9, UBUNTU-CVE-2020-5248.