dbcve.org
ZammadApplication

CVE-2024-36078

MEDIUM · 6.7 CVSS v3.1 Published 2024-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
In Zammad before 6.3.1, a Ruby gem bundled by Zammad is installed with world-writable file permissions. This allowed a local attacker on the server to modify the gem's files, injecting arbitrary code into Zammad processes (which run with the environment and permissions of the Zammad user).

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

A Ruby gem bundled with Zammad is installed with world-writable file permissions, allowing a local attacker to modify gem files and inject arbitrary code into Zammad processes running under the Zammad user account.

MitigationUpgrade to Zammad version 6.3.1 or later to receive the patched gem with correct permissions, or manually correct file permissions on the affected gem to remove world-writable access.

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

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

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. Identify Zammad installation and version
    Run command: zammad --version or check package manager (dpkg -l | grep zammad, rpm -qa | grep zammad)
    Affected if Zammad version is exactly 6.3.0
  2. Locate Zammad bundled Ruby gems directory
    Common paths: /opt/zammad/vendor/bundle/gems/ or /usr/share/zammad/vendor/bundle/gems/ - find gem directory under Zammad installation
    Affected if Gem directory exists under Zammad install path
  3. Check file permissions on gem files
    Run: find <gem_path> -type f -perm -002 to find world-writable files, or ls -la to manually inspect permissions
    Affected if Any .rb gem files or the gem directory itself shows world-writable (o+w) permissions
  4. Verify gem ownership and permissions are misconfigured
    Run: stat -c '%a %n' on gem files - permissions like 777, 666, or directories with 775/777 indicate the vulnerability
    Affected if Gem files or directories have permissions that allow write access to other users (world-writable bits set)

User is affected if Zammad version is exactly 6.3.0 AND any bundled gem files have world-writable (o+w) permission bits set, allowing local users to modify gem code.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Zammad version 6.3.1 or later to receive the patched gem with correct permissions, or manually correct file permissions on the affected gem to remove world-writable access.

Recommended fix Moderate confidence

Zammad 6.3.1

  1. 1. Back up your current Zammad installation and database before proceeding with any upgrade.
  2. 2. Download Zammad version 6.3.1 or later from the official Zammad website (zammad.com).
  3. 3. Stop the Zammad service to prevent active connections during upgrade.
  4. 4. Upgrade Zammad to version 6.3.1 by following the official upgrade instructions for your installation method (package manager, Docker, or source).
  5. 5. After upgrade, verify that the bundled Ruby gem no longer has world-writable permissions (permissions should be 755 or more restrictive).
  6. 6. Start the Zammad service and confirm the application runs correctly.
  7. 7. Verify the Zammad version is 6.3.1 or later using the web interface or command line.

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

Fix this in Zammad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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