XSS in GLPI
glpi-project · GLPI
In GLPI before version 9.4.6 there are multiple related stored XSS vulnerabilities. The package is vulnerable to Stored XSS in the comments of items in the Knowledge base. Adding a comment with content "<script>alert(1)</script>" reproduces the attack. This can be exploited by a user with administrator privileges in the User-Agent field. It can also be exploited by an outside party through the following steps: 1. Create a user with the surname `" onmouseover="alert(document.cookie)` and an empty first name. 2. With this user, create a ticket 3. As an administrator (or other privileged user) open the created ticket 4. On the "last update" field, put your mouse on the name of the user 5. The XSS fires This is fixed in version 9.4.6.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 3/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.How attackers get in
What they do
What can follow
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 5 May 2020. No public exploit code or confirmed exploitation is recorded.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
3 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order 3Initial AccessTA0001
ExecutionTA0002
CollectionTA0009
Detection
0 rules for this CVE · 34 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2020-11036 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Drive-by CompromiseT11893 general rules
JavaScriptT1059.00729 general rules
- Adwind RAT / JRAThightest
- Adwind RAT / JRAT File Artifacthightest
- Csc.EXE Execution Form Potentially Suspicious Parenthightest
- Cscript/Wscript Uncommon Script Extension Executionhightest
- HackTool - CACTUSTORCH Remote Thread Creationhightest
- HackTool - Koadic Executionhightest
- HTML Help HH.EXE Suspicious Child Processhightest
- JXA In-memory Execution Via OSAScripthightest
Browser Session HijackingT11852 general rules
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.