weak CSRF tokens in GLPI (glpi-project GLPI)

CVE-2020-11035
HIGH 7.5

At a glance

Source
NVD
EPSS
EPSS 0.90 % · percentile 60 ()
State
PUBLISHED
Published
Updated
Assigner
GitHub_M
NVD status
Modified

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.

Weaknesses (CWE)

  • CWE-327 — Use of a Broken or Risky Cryptographic Algorithm

References

Scores

VersionScoreVectorScored by
CVSS 3.1HIGH 7.5CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:NGitHub_M
CVSS 3.1HIGH 7.5CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:NNVD · security-advisories@github.com (Secondary)
CVSS 3.1CRITICAL 9.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:NNVD · nvd@nist.gov (Primary)
CVSS 2.0MEDIUM 6.4AV:N/AC:L/Au:N/C:P/I:P/A:NNVD · nvd@nist.gov (Primary)

European references

Affected configurations (NVD CPE)

Affected products

ProductVersions
glpi-project · GLPIaffected > 0.83.3, < 9.4.6

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD