VDB

CVE-2020-11035

CVE-2020-11035 PUBLISHED CVSS 7.5 HIGH

weak CSRF tokens in GLPI

Reported by github_m · Published May 5, 2020

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.

Risk scores

CVSS 3.1
7.5
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N

Affected products

VendorProductVersions
glpi-projectGLPI> 0.83.3, < 9.4.6
glpi-projectGLPI> 0.83.3, < 9.4.6

Timeline

  • May 5, 2020 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Aug 4, 2024 CVE Updated
  • Sep 6, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2020-11035
vulnetix vdb fixes CVE-2020-11035

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-11035/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›