Ticket privilege escalation via automatic ownership assignment
Published Jul 15, 2024 · Updated Aug 1, 2024
Incorrect privilege assignment in OTRS 8.0.X, 2023.X, and 2024.X through 2024.4.x allows remote authenticated users to gain full ticket access. Inline editing of the Watch property applies RequiredLock by locking the ticket and automatically assigning the current read-only agent as its owner. Exploitation requires administrator-enabled RequiredLock for the Watch property while the default OwnerCheck remains enabled, after which the agent can read and modify the ticket.
Summary
What happened
Incorrect privilege assignment in OTRS 8.0.X, 2023.X, and 2024.X through 2024.4.x allows remote authenticated users to gain full ticket access. Inline editing of the Watch property applies RequiredLock by locking the ticket and automatically assigning the current read-only agent as its owner. Exploitation requires administrator-enabled RequiredLock for the Watch property while the default OwnerCheck remains enabled, after which the agent can read and modify the ticket.
The record
- CVE
- CVE-2024-23794
- Published
- Jul 15, 2024
- Updated
- Aug 1, 2024
- Vendor
- Centuran Consulting
- Product
- OTRS
- Classifications
- CWE-266, CAPEC-233, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 15, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=2023.x
- Affected versionversion=2024.x <=2024.4.x
- Affected versionversion=8.0.x
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