CVE-2020-10100 - CVE House
Back to Database
Status published Medium CVE-2020-10100

An issue was discovered in Zammad 3.0 through 3.2. It...

Vulnerability Description

An issue was discovered in Zammad 3.0 through 3.2. It allows for users to view ticket customer details associated with specific customers. However, the application does not properly implement access controls related to this functionality. As such, users of one company are able to access ticket data from other companies. Due to the multi-tenant nature of this application, users who can access ticket details from one organization to the next allows for users to exfiltrate potentially sensitive data of other companies.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2020-10100

Credits & Attribution

No credits recorded in the NVD database.

References

More from zammad

View All →
CVE-2022-48023
Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker...
Medium 4.3
CVE-2022-48022
An issue in the component /api/v1/mentions of Zammad v5.3.0 allows...
Unknown 0
CVE-2022-48021
A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary...
Unknown 0
CVE-2022-40817
Zammad 5.2.1 has a fine-grained permission model that allows to...
Unknown 0
CVE-2022-40816
Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset...
Unknown 0

Affected Vendor

Affected Software

zammad
Vulnerable Versions:
1.0.0

Timeline

Official Publish: March 5th, 2020
Last Modified: August 4th, 2024
Added to House: July 21st, 2026

CVSS Vectors

V3: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.