Use of a Broken or Risky Cryptographic Algorithm Affecting glpi package, versions *


Severity

Recommended
0.0
critical
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

Exploit Maturity
Not Defined
EPSS
0.26% (66th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIAN8-GLPI-568615
  • published7 May 2020
  • disclosed5 May 2020

Introduced: 5 May 2020

CVE-2020-11035  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

There is no fixed version for Debian:8 glpi.

NVD Description

Note: Versions mentioned in the description apply only to the upstream glpi package and not the glpi package as distributed by Debian. See How to fix? for Debian:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1