GLPI < 9.4.6 - Use of Hard-coded Credentials via Default GLPIKEY
Title source: llmExploitation Summary
EIP tracks 3 public exploits for CVE-2020-5248. PoCs published by venomnis, Mkway.
AI-analyzed exploit summary This repository contains a functional PoC for CVE-2020-5248, demonstrating the decryption of sensitive data in GLPI using the default encryption key. The provided PHP script decrypts base64-encoded strings using the hardcoded 'GLPIKEY'.
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.
Exploits (3)
This repository contains a functional PoC for CVE-2020-5248, demonstrating the decryption of sensitive data in GLPI using the default encryption key. The provided PHP script decrypts base64-encoded strings using the hardcoded 'GLPIKEY'.
This repository provides a functional proof-of-concept for CVE-2020-5248, an information disclosure vulnerability in GLPI. It includes a Dockerized environment for testing and a PHP script to decrypt sensitive data.
This repository contains a functional PoC for CVE-2020-5248, which exploits a default encryption key in GLPI before version 9.4.6. The provided PHP script decrypts sensitive data encrypted with the hardcoded key 'GLPI£i'snarss'ç'.
References (2)
Scores
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N