dbcve.org
ZammadApplication

CVE-2024-33666

HIGH · 8.6 CVSS v3.1 Published 2024-04-26
Fix available
A fix is available. Upgrade to 6.3.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue was discovered in Zammad before 6.3.0. Users with customer access to a ticket could have accessed time accounting details of this ticket via the API. This data should be available only to agents.

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 before 6.3.0 contains a broken access control vulnerability in its API where customer users (non-privileged end users) could access time accounting details (tracking time entries, billable hours) associated with tickets via direct API calls. The API endpoint failed to enforce role-based authorization, allowing any authenticated user with ticket access to retrieve internal time accounting data that should be restricted to agent-level permissions.

MitigationUpgrade Zammad to version 6.3.0 or later which includes proper authorization checks for time accounting API endpoints. If immediate upgrade is not possible, review API access logs for unauthorized time accounting data access by customer-role users.

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:>= 6.2.0, < 6.3.0= 6.3.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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

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. Check installed Zammad version
    Run `zammad --version` or check the application footer in the web UI. Also check `/opt/zammad/config/initializers/version.rb` if available.
    Affected if Version is 6.2.0 through 6.3.0 (inclusive)
  2. Identify if time accounting feature is enabled
    Navigate to Admin > Settings > Time Accounting (or check database setting `time_accounting` in `settings` table). Query: `SELECT name, value FROM settings WHERE name LIKE '%time_accounting%';`
    Affected if Time accounting is enabled (value is true/1) in the Zammad instance
  3. Verify API access control for time accounting endpoint
    Make an authenticated API request as a customer user to `/api/v1/time_accounting` or `/api/v1/tickets/{id}/time_accounting` endpoint. Compare response against expected authorization behavior.
    Affected if Customer-role users can successfully retrieve time accounting data via API without receiving 403 Forbidden errors
  4. Review user role assignments
    Check Admin > Users to identify accounts with 'customer' role. Specifically look for customer users who have access to tickets that contain time accounting entries.
    Affected if Customer users exist in the system and have ticket access while time accounting data is present on those tickets

You are affected if running Zammad version 6.2.0 through 6.3.0, time accounting is enabled, and customer-role users can access time accounting data via the API.

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 6.3.0 or later
Fixed in 6.3.0
Interim mitigation

Upgrade Zammad to version 6.3.0 or later which includes proper authorization checks for time accounting API endpoints. If immediate upgrade is not possible, review API access logs for unauthorized time accounting data access by customer-role users.

Recommended fix High confidence

Zammad 6.3.1 or later stable release

  1. 1. Back up your current Zammad database and configuration files.
  2. 2. Check your current Zammad version using the admin interface or command line.
  3. 3. Review Zammad upgrade documentation for your deployment method (package, source, Docker, etc.).
  4. 4. Stop the Zammad service before upgrading.
  5. 5. Upgrade to Zammad version 6.3.1 or later stable release.
  6. 6. Verify the upgrade completed successfully.
  7. 7. Test that customer users can no longer access time accounting details via the API.
  8. 8. Restart Zammad services.
Caveat Review release notes for any breaking changes between your current version and 6.3.x; ensure plugin/compatibility checks are performed

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

Fix this in Zammad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33666 — 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-2024-33666 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