Database disclosure via unescaped ticket field merge
Published May 5, 2020 · Updated Aug 4, 2024
SQL injection in GLPI before 9.4.6 allows remote authenticated users with technician access to alter queries through ticket fields. The addme_assign and addme_observer paths merge stored ticket fields into update input without escaping them, causing crafted description text to become SQL syntax. A technician must save the payload in an existing ticket and invoke either action, exposing database contents and permitting limited data modification.
Summary
What happened
SQL injection in GLPI before 9.4.6 allows remote authenticated users with technician access to alter queries through ticket fields. The addme_assign and addme_observer paths merge stored ticket fields into update input without escaping them, causing crafted description text to become SQL syntax. A technician must save the payload in an existing ticket and invoke either action, exposing database contents and permitting limited data modification.
The record
- CVE
- CVE-2020-11032
- Published
- May 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- GLPI Project
- Product
- GLPI
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 9.4.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream advisory reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo