CVE-2020-5248 - CVE House

Back to Database

Status published High CVE-2020-5248

Public GLPIKEY can be used to decrypt any data in GLPI

7.2 CVSS

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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2020-5248

Check My Exposure

Credits & Attribution

No credits recorded in the NVD database.

References

More from glpi-project

View All →

GLPI has an unauthenticated SQL injection through the inventory endpoint

GLPI vulnerable to unauthorized access to restricted Knowledge Base items through the API

GLPI incorrectly authorizes access to documents

GLPI Vulnerable to Unauthenticated Stored XSS on the Inventory page

GLPI permits reservation modification by unauthorized users

Affected Vendor

glpi-project

View all reports →

Affected Software

glpi

Vulnerable Versions:

< 9.4.6

Timeline

Official Publish: May 12th, 2020

Last Modified: August 4th, 2024

Added to House: July 21st, 2026

CVSS Vectors

V3: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N

Weaknesses (CWE)

MITRE ATT&CK TTPs

T1552 Unsecured Credentials

Credential Access

T1078 Valid Accounts

T1021 Remote Services

Lateral Movement

T1190 Exploit Public-Facing Application

T1098 Account Manipulation

Privilege Escalation