CVE-2022-40816
First published: Tue Sep 27 2022(Updated: )
Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset handling mechanism has logic to ensure that customer users are not able to see personal information of other users. This logic was not effective when used through a web socket connection, so that a logged-in attacker would be able to fetch personal data of other users by querying the Zammad API. This issue is fixed in , 5.2.2.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Zammad Zammad | >=5.2.0<5.2.2 |
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 Zammad version?
The vulnerability ID of this Zammad version is CVE-2022-40816.
What is the severity of CVE-2022-40816?
The severity of CVE-2022-40816 is medium with a severity value of 6.5.
How does the asset handling mechanism in Zammad ensure the privacy of customer users?
The asset handling mechanism in Zammad has logic to ensure that customer users are not able to see personal information of other users.
How was the privacy logic in Zammad's asset handling mechanism bypassed in this vulnerability?
The privacy logic in Zammad's asset handling mechanism was not effective when used through a web socket connection, allowing a logged-in attacker to view personal information of other users.
Where can I find more information about this vulnerability?
You can find more information about this vulnerability in the Zammad advisory: https://zammad.com/de/advisories/zaa-2022-09
- collector/nvd-index
- agent/references
- agent/severity
- agent/author
- agent/tags
- agent/type
- agent/event
- agent/weakness
- agent/description
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- vendor/zammad
- canonical/zammad zammad
- version/zammad zammad/5.2.0