Authenticated conversation disclosure via missing participant check
Published May 31, 2022 · Updated Aug 3, 2024
Authorization bypass in Trudesk before 1.2.3 allows remote authenticated users to read conversations they do not participate in. The getConversation controller returns messages without verifying that req.user appears in the conversation's participant list. Any signed-in account with a valid conversation identifier can disclose that conversation's contents; the published patch shows no write capability.
Summary
What happened
Authorization bypass in Trudesk before 1.2.3 allows remote authenticated users to read conversations they do not participate in. The getConversation controller returns messages without verifying that req.user appears in the conversation's participant list. Any signed-in account with a valid conversation identifier can disclose that conversation's contents; the published patch shows no write capability.
The record
- CVE
- CVE-2022-1947
- Published
- May 31, 2022
- Updated
- Aug 3, 2024
- Vendor
- Trudesk, Inc.
- Product
- Trudesk
- Classifications
- CWE-480, T1213.005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 31, 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.3
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