CVE-2020-11031

Insecure encryption algorithm in GLPI

Published Sep 23, 2020 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2020-3416 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.
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 4, 2024, 11:21 AM
Reserved
Mar 30, 2020, 12:00 AM
Status
Modified
Published
Sep 23, 2020, 4:15 PM
Modified
Jun 17, 2026, 2:48 AM