CVE-2020-11031

Insecure encryption algorithm in GLPI

State: Published
Severity: 7.8 High
Published: Sep 23, 2020
Updated: Aug 4, 2024
Reserved: Mar 30, 2020

Description

In GLPI before version 9.5.0, the encryption algorithm used is insecure. The security of the data encrypted relies on the password used, if a user sets a weak/predictable password, an attacker could decrypt data. This is fixed in version 9.5.0 by using a more secure encryption library. The library chosen is sodium.

Scores

CVSS	Score	Vector	Source
3.1	7.8 High	CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N	GitHub_M

Weaknesses

CWE-327 Use of a Broken or Risky Cryptographic Algorithm

Affected Products

Product	Versions
GLPIglpi-project	< 9.5.0Affected

References

https://github.com/glpi-project/glpi/security/advisories/GHSA-7xwm-4vjr-jvqh
https://github.com/glpi-project/glpi/commit/f1ae6c8481e5c19a6f1801a5548cada45702e01a#diff-b5d0ee8c97c7abd7e3fa29b9a27d1780

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.