dbcve.org
ZammadApplication

CVE-2022-40816

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-27
Fix available
A fix is available. Upgrade to 5.2.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Zammad 5.2.1 has an Incorrect Access Control vulnerability where the asset handling mechanism's privacy protection logic (preventing customer users from seeing other users' personal data) is bypassed when the API is accessed through a web socket connection, allowing authenticated attackers to enumerate and retrieve personal information of other users.

MitigationUpgrade Zammad to version 5.2.2 or later to apply the vendor fix. Verify that web socket access controls properly enforce the same access restrictions as HTTP requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZammadApplication
Affected:>= 5.2.0, < 5.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Zammad version
    Run `zammad --version` or check the package manager for the installed zammad package version. On the server, you may also find version info in the application footer of the web UI or via `/api/v1/health` endpoint.
    Affected if The version is >= 5.2.0 and < 5.2.2 (such as 5.2.0 or 5.2.1)
  2. Verify web socket endpoint accessibility
    Check if the web socket API endpoint (typically at `/ws` or `/api/v1/websocket`) is reachable and responds to connection requests. This can be tested by attempting a web socket connection from an authenticated session or checking network listener configurations.
    Affected if Web socket connections to the Zammad API are permitted and functional
  3. Confirm presence of customer user roles
    Review user roles in Zammad admin panel under Users > Roles. Identify if any roles with limited permissions (such as Customer) exist that should have restricted access to personal data.
    Affected if Customer or other limited-privilege user roles exist in the system
  4. Test web socket API for access control bypass
    Using an authenticated session as a customer user, connect to the web socket endpoint and attempt to query user asset endpoints (such as user data or personal information endpoints) that should normally be restricted. Compare responses to HTTP API behavior.
    Affected if Web socket requests return personal data of other users that should be restricted

If Zammad version is between 5.2.0 and 5.2.1 inclusive and web socket access to the API is enabled, the privacy protection bypass is present and other users personal data may be enumerable by authenticated customer users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.2.2 or later
Fixed in 5.2.2
Interim mitigation

Upgrade Zammad to version 5.2.2 or later to apply the vendor fix. Verify that web socket access controls properly enforce the same access restrictions as HTTP requests.

Recommended fix High confidence

5.2.2

  1. Verify current Zammad version by checking the admin interface or running: zammad --version
  2. Back up the Zammad database and configuration files before upgrading
  3. Upgrade Zammad to version 5.2.2. For package-based installations, use: apt-get update && apt-get install zammad (Debian/Ubuntu) or yum update zammad (RHEL/CentOS)
  4. For Docker installations, update the image tag to the 5.2.2 release and recreate containers
  5. Verify the upgrade was successful by checking the Zammad version again
  6. Confirm the web socket authorization fix is working by testing that users cannot access other users' personal data through the API
Caveat Minor patch upgrade within 5.2.x - minimal risk, primarily a security fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zammad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-40816 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data