Authenticated account enumeration via mismatched IDOR tokens
Published Mar 8, 2021 · Updated Aug 3, 2024
Authorization bypass in GLPI before 9.5.4 allows remote authenticated users to enumerate item names and user logins through solution search. The knowledge-base dropdown accepts a user-controlled item_itemtype and incremental item_items_id while its IDOR token fails to bind the requested object type. Any valid account with access to an open ticket's Solution form can substitute User and guess identifiers, exposing names and login identifiers without modifying data.
Summary
What happened
Authorization bypass in GLPI before 9.5.4 allows remote authenticated users to enumerate item names and user logins through solution search. The knowledge-base dropdown accepts a user-controlled item_itemtype and incremental item_items_id while its IDOR token fails to bind the requested object type. Any valid account with access to an open ticket's Solution form can substitute User and guess identifiers, exposing names and login identifiers without modifying data.
The record
- CVE
- CVE-2021-21324
- Published
- Mar 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- GLPI Project
- Product
- GLPI
- Classifications
- CWE-639, T1087
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.5.4
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 solution-search reproduction procedureproof 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