dbcve.org
ZammadApplication

CVE-2023-50454

MEDIUM · 5.9 CVSS v3.1 Published 2023-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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.2.0. In several subsystems, SSL/TLS was used to establish connections to external services without proper validation of hostname and certificate authority. This is exploitable by man-in-the-middle attackers.

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 version 6.2.0 fails to properly validate SSL/TLS certificates and hostnames when establishing connections to external services, allowing man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent certificates.

MitigationUpgrade Zammad to version 6.2.0 or later to resolve the improper SSL/TLS certificate validation. Verify all external integrations function correctly after the upgrade.

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.1.0= 6.2.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/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
    Access the Zammad admin interface at /#system/information or run command: zammad --version
    Affected if Version is before 6.2.0 (e.g., 6.1.x, 6.0.x, or earlier)
  2. Identify external integrations using SSL/TLS
    Review Zammad admin settings under Apps, Channels (Email, Microsoft 365, Google, etc.), and Webhook configurations for any external service connections
    Affected if Any external integration (email servers, API endpoints, OAuth providers, webhooks) is configured and uses HTTPS
  3. Check if SSL verification is enforced in Email channel
    Navigate to Admin > Channels > Email > inbound/outbound settings and verify 'Verify certificate' or similar SSL verification options are enabled
    Affected if SSL certificate verification is disabled or not enforced for email connections
  4. Review HTTP backend configuration
    Inspect config/environments/production.rb or environment variables for any setting that disables SSL verification (e.g., 'OpenSSL::SSL::VERIFY_NONE', 'ssl_verify_mode'), or check /api/v1/http_backend/config endpoint
    Affected if SSL/TLS certificate verification is explicitly disabled in application configuration

You are affected if your Zammad version is before 6.2.0 and you have any external integrations configured that use HTTPS connections without proper certificate validation.

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 Zammad to version 6.2.0 or later to resolve the improper SSL/TLS certificate validation. Verify all external integrations function correctly after the upgrade.

Recommended fix Moderate confidence

Zammad 6.3.0 or later

  1. 1. Back up your current Zammad installation and database
  2. 2. Check the current installed version using: zammad --version
  3. 3. Review Zammad's upgrade documentation for your deployment method (package or source)
  4. 4. Upgrade to Zammad version 6.3.0 or later which contains the fix for improper SSL/TLS certificate validation
  5. 5. After upgrade, verify the version: zammad --version
  6. 6. Test that external service connections (email, webhook, API integrations) work correctly
  7. 7. Confirm the SSL/TLS certificate validation is now properly enforced
Caveat Review release notes for any configuration or feature changes between your current version and 6.3.0; minor version upgrades typically have low risk but always test in staging first

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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