CVE-2022-35487
First published: Mon Aug 08 2022(Updated: )
Zammad 5.2.0 suffers from Incorrect Access Control. Zammad did not correctly perform authorization on certain attachment endpoints. This could be abused by an unauthenticated attacker to gain access to attachments, such as emails or attached files.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Zammad Zammad | =5.2.0 | |
| Zammad Zammad | =5.2.0-alpha |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID of this issue?
The vulnerability ID of this issue is CVE-2022-35487.
What is the severity of CVE-2022-35487?
The severity of CVE-2022-35487 is high.
What is the affected version of Zammad?
Zammad version 5.2.0 and 5.2.0-alpha are affected.
What is the impact of this vulnerability?
This vulnerability allows an unauthenticated attacker to gain access to attachments, such as emails or attached files.
Is there a fix available for CVE-2022-35487?
Currently, there is no information available about a fix for CVE-2022-35487. It is recommended to follow the security advisory from Zammad for updates.
- collector/nvd-index
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/description
- agent/tags
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- vendor/zammad
- canonical/zammad zammad
- version/zammad zammad/5.2.0
- version/zammad zammad/5.2.0-alpha