CVE-2022-39323 SQL Injection on REST API in GLPI
An attacker can perform time-based SQL injection via the REST API user_token endpoint to read or modify data in GLPI.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-39323?
CVE-2022-39323 is a high-severity SQL injection vulnerability in Glpi-Project Glpi, published on 3 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
GLPI stands for Gestionnaire Libre de Parc Informatique. GLPI is a Free Asset and IT Management Software package that provides ITIL Service Desk features, licenses tracking and software auditing. Time based attack using a SQL injection in api REST user_token. This issue has been patched, please upgrade to version 10.0.4. As a workaround, disable login with user_token on API Rest.
Weakness: CWE-89
Which versions are affected by CVE-2022-39323?
It affects 1 product.
Products include Glpi-Project Glpi.
How do I fix CVE-2022-39323?
No fix has been published for CVE-2022-39323 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2022-39323 being exploited?
There is no known exploitation of CVE-2022-39323 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-cp6q-9p4x-8hr9, UBUNTU-CVE-2022-39323.