Unauthorized ticket-tag changes via missing permission check
Published Feb 3, 2023 · Updated Aug 3, 2024
Incorrect access control in Zammad 5.3.0 allows remote authenticated users to change tags on their own customer tickets through the API. The ticket-tag update path does not require an agent role or ticket write permission before applying a requested tag change. A customer account is sufficient, and the impact is limited to unauthorized tag modification on tickets belonging to that customer.
Summary
What happened
Incorrect access control in Zammad 5.3.0 allows remote authenticated users to change tags on their own customer tickets through the API. The ticket-tag update path does not require an agent role or ticket write permission before applying a requested tag change. A customer account is sufficient, and the impact is limited to unauthorized tag modification on tickets belonging to that customer.
The record
- CVE
- CVE-2022-48023
- Published
- Feb 3, 2023
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 3, 2023CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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