CVE-2020-15226 SQL Injection in GLPI Search API
An attacker with an API account can exploit SQL injection in the search function to read sensitive database information.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2020-15226?
CVE-2020-15226 is a medium-severity SQL injection vulnerability in Glpi-Project Glpi, published on 7 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In GLPI before version 9.5.2, there is a SQL Injection in the API's search function. Not only is it possible to break the SQL syntax, but it is also possible to utilise a UNION SELECT query to reflect sensitive information such as the current database version, or database user. The most likely scenario for this vulnerability is with someone who has an API account to the system. The issue is patched in version 9.5.2. A proof-of-concept with technical details is available in the linked advisory.
Weakness: CWE-89
Which versions are affected by CVE-2020-15226?
It affects 1 product.
Products include Glpi-Project Glpi.
How do I fix CVE-2020-15226?
No fix has been published for CVE-2020-15226 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-2020-15226 being exploited?
There is no known exploitation of CVE-2020-15226 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-jwpv-7m4h-5gvc.