CVE-2020-11031 Insecure encryption algorithm in GLPI
An attacker can decrypt sensitive data if users set weak passwords due to GLPI's use of an insecure encryption algorithm.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2020-11031?
CVE-2020-11031 is a high-severity vulnerability in Glpi-Project Glpi, published on 23 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Weakness: CWE-327
Which versions are affected by CVE-2020-11031?
It affects 1 product.
Products include Glpi-Project Glpi.
How do I fix CVE-2020-11031?
No fix has been published for CVE-2020-11031 yet. Limit exposure of the affected software until one is available.
Is CVE-2020-11031 being exploited?
There is no known exploitation of CVE-2020-11031 in the wild and no public exploit code.
Other vulnerabilities in Glpi-Project Glpi
- CVE-2022-35914 Teclib GLPI Remote Code Execution
- CVE-2023-42802 GLPI vulnerable to unallowed PHP script execution
- CVE-2023-28849 GLPI vulnerable to SQL injection and Stored XSS via inventory agent request
- CVE-2022-35947 SQL injection in GLPI
- CVE-2022-31056 SQL injection with _actor parameter in GLPI
Sources
Also known as GHSA-7xwm-4vjr-jvqh, UBUNTU-CVE-2020-11031.