Authenticated script execution via ticket filters
Published May 16, 2022 · Updated Aug 3, 2024
Cross-site scripting in Trudesk before 1.2.2 allows remote authenticated users to execute JavaScript through ticket filters. The ticketsController.filter function used request parameters such as status, priority, groups, types, tags, assignee, and subject without applying xss() sanitization before constructing the filter. Exploitation requires a low-privilege authenticated session and a victim to load the crafted filter URL, enabling script execution in the victim's web context with confidentiality and integrity impact.
Summary
What happened
Cross-site scripting in Trudesk before 1.2.2 allows remote authenticated users to execute JavaScript through ticket filters. The ticketsController.filter function used request parameters such as status, priority, groups, types, tags, assignee, and subject without applying xss() sanitization before constructing the filter. Exploitation requires a low-privilege authenticated session and a victim to load the crafted filter URL, enabling script execution in the victim's web context with confidentiality and integrity impact.
The record
- CVE
- CVE-2022-1719
- Published
- May 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Trudesk, Inc.
- Product
- Trudesk
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 16, 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.2
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
- huntr bounty 790ba3fd-41e9-4393-8e2f-71161b56279bproof 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