Description
In GLPI after version 0.83.3 and before version 9.4.6, the CSRF tokens are generated using an insecure algorithm. The implementation uses rand and uniqid and MD5 which does not provide secure values. This is fixed in version 9.4.6.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-3420 | In GLPI after version 0.83.3 and before version 9.4.6, the CSRF tokens are generated using an insecure algorithm. The implementation uses rand and uniqid and MD5 which does not provide secure values. This is fixed in version 9.4.6. |
References
History
No history.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2024-08-04T11:21:14.511Z
Reserved: 2020-03-30T00:00:00.000Z
Link: CVE-2020-11035
No data.
Status : Modified
Published: 2020-05-05T22:15:12.823
Modified: 2026-06-17T02:48:54.800
Link: CVE-2020-11035
No data.
OpenCVE Enrichment
No data.
Weaknesses
-
CWE-327
Use of a Broken or Risky Cryptographic Algorithm
EUVD