Message-data alteration via unvalidated record references
Published May 31, 2022 · Updated Aug 3, 2024
Incorrect synchronization in Trudesk before 1.2.3 allows remote authenticated users to alter message data through the messaging API. The apiMessages.send handler updated a client-selected conversation and created a message with client-supplied conversation and owner identifiers without first resolving and validating either referenced record. A valid account and network access to the API are required; the public record does not identify a narrower role or fully describe the resulting effects.
Summary
What happened
Incorrect synchronization in Trudesk before 1.2.3 allows remote authenticated users to alter message data through the messaging API. The apiMessages.send handler updated a client-selected conversation and created a message with client-supplied conversation and owner identifiers without first resolving and validating either referenced record. A valid account and network access to the API are required; the public record does not identify a narrower role or fully describe the resulting effects.
The record
- CVE
- CVE-2022-1931
- Published
- May 31, 2022
- Updated
- Aug 3, 2024
- Vendor
- Trudesk, Inc.
- Product
- Trudesk
- Classifications
- CWE-662, CWE-821
- 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.
Public exploit references
- huntr.dev bounty exploit artifactproof of concept · unverified
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