Token disclosure via incomplete API field filtering
Published May 5, 2020 · Updated Aug 4, 2024
Information disclosure in GLPI 9.1 through 9.4.5 allows remote authenticated users to obtain other users' API and personal tokens. The User item API serializes complete user records while its field filter removes only passwords, leaving personal_token and api_token in responses. Exploitation requires an enabled API and a technician account with READ access to User items; exposed API tokens permit unauthorized data operations, while personal tokens reveal planning data.
Summary
What happened
Information disclosure in GLPI 9.1 through 9.4.5 allows remote authenticated users to obtain other users' API and personal tokens. The User item API serializes complete user records while its field filter removes only passwords, leaving personal_token and api_token in responses. Exploitation requires an enabled API and a technician account with READ access to User items; exposed API tokens permit unauthorized data operations, while personal tokens reveal planning data.
The record
- CVE
- CVE-2020-11033
- Published
- May 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- GLPI Project
- Product
- GLPI
- Classifications
- CWE-200, T1552
- 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.1, < 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
No public exploit references are available in this record.
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