CVE-2020-5248
GLPI Default Encryption Key Vulnerability
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.
INFO
Published Date :
May 12, 2020, 4:15 p.m.
Last Modified :
May 14, 2020, 5:08 p.m.
Source :
[email protected]
Remotely Exploitable :
No
Impact Score :
5.8
Exploitability Score :
0.8
Public PoC/Exploit Available at Github
CVE-2020-5248 has a 7 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2020-5248.
| URL | Resource |
|---|---|
| https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c | Patch Third Party Advisory |
| https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9 | Mitigation Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
You should think about upgrading your GLPI now
Go
None
CVE-2020-5248
PHP Dockerfile
Automatic monitor github cve using Github Actions
Python
None
None
Proof of Concept (PoC) for CVE-2020-5248.
PHP
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2020-5248 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2020-5248 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
May. 14, 2020
Action Type Old Value New Value Added CVSS V2 NIST (AV:N/AC:L/Au:N/C:P/I:N/A:N) Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Changed Reference Type https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c No Types Assigned https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c Patch, Third Party Advisory Changed Reference Type https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9 No Types Assigned https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9 Mitigation, Third Party Advisory Added CWE NIST CWE-798 Added CPE Configuration OR *cpe:2.3:a:glpi-project:glpi:*:*:*:*:*:*:*:* versions up to (excluding) 9.4.6 -
CVE Modified by [email protected]
May. 12, 2020
Action Type Old Value New Value Changed 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. 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.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2020-5248 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2020-5248
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.07 }} 0.00%
score
0.28177
percentile