Ticket-history disclosure via spoofed Cc authorization
Published Oct 12, 2024 · Updated Oct 16, 2024
Authentication bypass in Zendesk before 2024-07-02 allows remote attackers to read ticket history through spoofed email messages. Inbound email processing trusts a spoofed sender, extracts Cc recipients, and grants them ticket-view authorization without adequate sender verification. Exploitation requires a predictable per-ticket support address, the requester's email address, and a public support portal; it exposes ticket history without reported modification or disruption.
Summary
What happened
Authentication bypass in Zendesk before 2024-07-02 allows remote attackers to read ticket history through spoofed email messages. Inbound email processing trusts a spoofed sender, extracts Cc recipients, and grants them ticket-view authorization without adequate sender verification. Exploitation requires a predictable per-ticket support address, the requester's email address, and a public support portal; it exposes ticket history without reported modification or disruption.
The record
- CVE
- CVE-2024-49193
- Published
- Oct 12, 2024
- Updated
- Oct 16, 2024
- Vendor
- Zendesk
- Product
- Zendesk
- Classifications
- CWE-290, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 12, 2024CVE publishedPublication date reported by the CVE source.
- Oct 16, 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=0 <20240702
What conditions does exploitation require?
What is affected?
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
- Zendesk spoofed-Cc ticket access reproductionfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Zendesk ticket access chained to Slack account takeoverexploit chain
- Ticket-history access reproduced across vulnerable Zendesk instancesreported exploitation
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