Use of Hard-coded Credentials Affecting glpi package, versions *


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

Exploit Maturity
Not Defined
EPSS
0.07% (34th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN8-GLPI-569160
  • published18 May 2020
  • disclosed12 May 2020

Introduced: 12 May 2020

CVE-2020-5248  (opens in a new tab)
CWE-798  (opens in a new tab)

How to fix?

There is no fixed version for Debian:8 glpi.

NVD Description

Note: Versions mentioned in the description apply only to the upstream glpi package and not the glpi package as distributed by Debian. See How to fix? for Debian:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1