CVE-2020-11031

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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:glpi-project:glpi:*:*:*:*:*:*:*:*

History

21 Nov 2024, 04:56

Type Values Removed Values Added
CVSS v2 : 5.0
v3 : 7.5
v2 : 5.0
v3 : 7.8
References () https://github.com/glpi-project/glpi/commit/f1ae6c8481e5c19a6f1801a5548cada45702e01a#diff-b5d0ee8c97c7abd7e3fa29b9a27d1780 - Patch, Third Party Advisory () https://github.com/glpi-project/glpi/commit/f1ae6c8481e5c19a6f1801a5548cada45702e01a#diff-b5d0ee8c97c7abd7e3fa29b9a27d1780 - Patch, Third Party Advisory
References () https://github.com/glpi-project/glpi/security/advisories/GHSA-7xwm-4vjr-jvqh - Third Party Advisory () https://github.com/glpi-project/glpi/security/advisories/GHSA-7xwm-4vjr-jvqh - Third Party Advisory

Information

Published : 2020-09-23 16:15

Updated : 2024-11-21 04:56


NVD link : CVE-2020-11031

Mitre link : CVE-2020-11031

CVE.ORG link : CVE-2020-11031


JSON object : View

Products Affected

glpi-project

  • glpi
CWE
CWE-327

Use of a Broken or Risky Cryptographic Algorithm