Account takeover via caller-selected user update
Published Jun 20, 2022 · Updated Aug 3, 2024
Improper privilege management in Trudesk before 1.2.4 allows remote authenticated users to modify other users' accounts through its API. The /api/v1/users/{username} path accepts a caller-selected account and privileged password, role, and group fields, while the fixed profile handler binds the username to the authenticated account and excludes role and group changes. Any valid user access token reaches the affected operation, enabling account takeover or assignment of administrative privileges.
Summary
What happened
Improper privilege management in Trudesk before 1.2.4 allows remote authenticated users to modify other users' accounts through its API. The /api/v1/users/{username} path accepts a caller-selected account and privileged password, role, and group fields, while the fixed profile handler binds the username to the authenticated account and excludes role and group changes. Any valid user access token reaches the affected operation, enabling account takeover or assignment of administrative privileges.
The record
- CVE
- CVE-2022-2023
- Published
- Jun 20, 2022
- Updated
- Aug 3, 2024
- Vendor
- Trudesk, Inc.
- Product
- Trudesk
- Classifications
- CWE-269, CWE-648, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 20, 2022CVE 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=unspecified <1.2.4
What conditions does exploitation require?
What is affected?
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