Security readout for executives and security teams
Plain-English summary
CVE-2021-35302 is an access-control weakness in Zammad versions 1.0.x through 4.0.0 involving linked tickets. The public CVE text says remote attackers could obtain sensitive information. Available source data does not provide CVSS, exploit details, or a specific fixed version.
Executive priority
Prioritize this for any Zammad helpdesk containing sensitive operational, customer, or security tickets. Business urgency is highest where external users can access tickets or where linked tickets may expose confidential information.
Technical view
The issue is described as incorrect access control for linked tickets in Zammad 1.0.x up to 4.0.0. The security impact is unauthorized disclosure of sensitive information. The provided sources do not identify CWE, attack prerequisites, authentication requirements, or the vendor remediation details beyond the advisory reference.
Likely exposure
Organizations running Zammad 1.0.x through 4.0.0 may be exposed, especially where ticket data contains customer, employee, incident, or security information. Exposure cannot be confirmed from product inventory alone; linked-ticket access behavior should be validated.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat this as a plausible remote information-disclosure risk, not a confirmed exploited vulnerability, based on the available sources.
Researcher notes
Evidence is limited to the CVE description and Zammad advisory reference. No CVSS vector, CWE, exploit status, or remediation details are included in the source bundle. Avoid assuming authentication requirements or fixed versions without consulting the advisory.
Mitigation direction
- Identify any Zammad deployments and record exact versions.
- Review Zammad advisory ZAA-2021-04 for fixed releases and upgrade guidance.
- Prioritize upgrade or remediation for internet-facing or sensitive helpdesk instances.
- Restrict ticket access to necessary users until remediation is confirmed.
- Review handling of linked tickets containing sensitive data.
Validation and detection
- Confirm whether any deployment runs Zammad 1.0.x through 4.0.0.
- Check linked-ticket permissions using authorized test accounts.
- Verify unauthorized users cannot view sensitive linked-ticket information.
- Review access logs for unusual linked-ticket access patterns.
- Document remediation status against the Zammad advisory.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-35302 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://zammad.com/en/advisories/zaa-2021-04CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.