Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2022-40816 | First vendor Publication | 2022-09-27 |
| Vendor | Cve | Last vendor Modification | 2023-08-08 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | |||
|---|---|---|---|
| Overall CVSS Score | 6.5 | ||
| Base Score | 6.5 | Environmental Score | 6.5 |
| impact SubScore | 3.6 | Temporal Score | 6.5 |
| Exploitabality Sub Score | 2.8 | ||
| Attack Vector | Network | Attack Complexity | Low |
| Privileges Required | Low | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | High |
| Integrity Impact | None | Availability Impact | None |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| 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. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40816 |
CPE : Common Platform Enumeration
Sources (Detail)
| Source | Url |
|---|---|
| MISC | https://zammad.com/de/advisories/zaa-2022-09 |
Alert History
| Date | Informations |
|---|---|
| 2023-08-09 17:27:56 |
|
| 2022-09-29 17:27:14 |
|
| 2022-09-28 17:27:11 |
|
| 2022-09-28 05:27:11 |
|
