CVE-2023-29867
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 · uneditedZammad 5.3.x (Fixed 5.4.0) is vulnerable to Incorrect Access Control. An authenticated attacker could gain information about linked accounts of users involved in their tickets using the Zammad API.
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 confidenceZammad 5.3.x contains an Incorrect Access Control vulnerability in its API where an authenticated attacker can enumerate information about linked accounts (such as third-party integrations or OAuth connections) belonging to users who are involved in their tickets. This is a classic Insecure Direct Object Reference (IDOR) flaw where the API fails to properly validate that the requesting user has authorization to view these linked account details.
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>= 5.3.0, < 5.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Zammad versionLocate the installed Zammad version number (typically visible in the web UI footer, about page, or via command-line tools provided by Zammad)Affected if The installed version is 5.3.x (any version from 5.3.0 up to but not including 5.4.0)
-
Verify API is accessibleConfirm that the Zammad API endpoint is reachable and accepts authenticated requestsAffected if API access is enabled and users can authenticate to it
-
Identify users with linked accountsReview user accounts to determine if any users have third-party integrations, OAuth connections, or linked external accounts configuredAffected if Any user accounts have linked third-party or OAuth integrations configured
-
Check ticket assignmentDetermine if there are any tickets where the requesting user has access (as requester, owner, or participant) to tickets belonging to other usersAffected if The authenticated user has access to tickets involving other users who have linked accounts
You are affected if your Zammad version is 5.3.0 or higher but below 5.4.0, and your installation has the API enabled with users who have linked third-party or OAuth accounts accessible to other authenticated users through ticket involvement.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.4.0
Upgrade to Zammad version 5.4.0 or later, which contains the fix for this access control vulnerability.
5.4.0
- 1. Back up your current Zammad installation and database before upgrading.
- 2. Check the official Zammad upgrade documentation for your installation method (e.g., package manager, Docker, source).
- 3. Upgrade Zammad to version 5.4.0 or later.
- 4. Verify the upgrade was successful by logging in and checking the version number.
- 5. Test that the API functionality works correctly after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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