nday
CVE-2020-5248 GHSA-j222-j9mf-h6j9

Public GLPIKEY can be used to decrypt any data in GLPI

glpi-project / glpi

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

hard-coded credentials
CWE-798, stated by the CNA GitHub_M, NVD's analysts, and NVD, republishing [email protected]
local
AV:L in CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N (CVSS 3.1) from the CNA GitHub_M
no user interaction
UI:N in CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N (CVSS 3.1) from the CNA GitHub_M
GLPI
affected products in the CVE record: glpi-project · glpiCPE names NVD's analysts give as vulnerable: a:glpi-project:glpi
monitoring / logging / IT management
affected products in the CVE record: glpi-project · glpiCPE names NVD's analysts give as vulnerable: a:glpi-project:glpithe product type of GLPI in nday's product registry
stage
DIS
disclosed
cvss
7.2 HIGH v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2020-05-12T16:05Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:H
High: administrative or similar privileges
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 3.1 vector from the CVE record, scored by the CNA GitHub_M.

Event log

+DISdisclosed

CVE record published by GitHub_M. CVSS 7.2, high.

src cvelist · nday , bulk import · raw
{
  "id": 215269,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2020-5248",
  "occurred_at": "2020-05-12T16:05:17Z",
  "observed_at": "2026-11-13T05:37:06.265724Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N",
      "version": "3.1",
      "base_score": 7.2,
      "base_severity": "HIGH"
    },
    "state": "PUBLISHED",
    "date_published": "2020-05-12T16:05:17.000Z",
    "assigner_short_name": "GitHub_M"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.