5 Medium
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
7.2 High
CVSS3
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
HIGH
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
NONE
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
0.001 Low
EPSS
Percentile
30.3%
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.
github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c
github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9
launchpad.net/bugs/cve/CVE-2020-5248
nvd.nist.gov/vuln/detail/CVE-2020-5248
security-tracker.debian.org/tracker/CVE-2020-5248
www.cve.org/CVERecord?id=CVE-2020-5248
5 Medium
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
7.2 High
CVSS3
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
HIGH
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
NONE
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
0.001 Low
EPSS
Percentile
30.3%