dbcve.org
OtrsApplication

CVE-2022-32740

MEDIUM · 5.3 CVSS v3.1 Published 2022-06-13
Fix available
A fix is available. Upgrade to 7.0.35 / 8.0.23 or later.
See remediation →
62/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
A reply to a forwarded email article by a 3rd party could unintensionally expose the email content to the ticket customer under certain circumstances.

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 · moderate confidence

This is an information disclosure vulnerability in a ticketing/helpdesk system where replies to forwarded email articles can unintentionally expose email content to the ticket customer. When a third party replies to a forwarded email article, the system fails to properly restrict access, allowing the ticket customer to view email content they should not have access to.

MitigationImplement proper access control checks on forwarded email content to ensure replies are only visible to authorized parties, and validate that ticket customers cannot view third-party email exchanges.

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
OtrsApplication
Affected:>= 7.0.0, < 7.0.35>= 8.0.0, < 8.0.23

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify OTRS version
    Locate the OTRS installation directory and check the version file (typically VERSION or Kernel/Config.pm) or run the OTRS system information command
    Affected if The installed version is 7.0.0 through 7.0.34, or 8.0.0 through 8.0.22
  2. Confirm ticketing system is active
    Verify that OTRS is actively running as a helpdesk system with customer-facing ticket access enabled
    Affected if The system processes customer tickets and allows customers to view ticket articles online
  3. Check email article handling
    Inspect the system configuration for email article processing, specifically whether incoming emails are stored as articles and can be forwarded
    Affected if Email articles are stored as ticket articles and can be forwarded to third parties
  4. Verify customer access to articles
    Review the ticket/article access control settings to confirm whether customers can access all article types including forwarded email content
    Affected if Customers have access to view email articles without restrictions on reply visibility
  5. Test third-party reply visibility
    Create a test ticket with a forwarded email article, then have a third party reply to that forwarded email and verify if the customer can see the third-party reply
    Affected if Customers can view replies from third parties to forwarded email articles that they should not have access to

A system is affected if it runs OTRS version 7.0.0-7.0.34 or 8.0.0-8.0.22, uses email article forwarding, and allows customers to view third-party replies to forwarded emails.

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 7.0.35 / 8.0.23 or later
Fixed in 7.0.358.0.23
Interim mitigation

Implement proper access control checks on forwarded email content to ensure replies are only visible to authorized parties, and validate that ticket customers cannot view third-party email exchanges.

Recommended fix Moderate confidence

OTRS 7.0.35 or later / OTRS 8.0.23 or later

  1. Verify current OTRS version by checking the admin panel or running: bin/otrs.Console.pl Admin::Package::List
  2. Backup the OTRS database and configuration files before upgrading
  3. For OTRS 7.x: Download OTRS 7.0.35 or later from the official OTRS website
  4. For OTRS 8.x: Download OTRS 8.0.23 or later from the official OTRS website
  5. Stop the OTRS services: systemctl stop otrs or perl bin/otrs.Daemon.pl stop
  6. Extract the new version to the OTRS directory, overwriting existing files
  7. Run the upgrade script: bin/otrs.Console.pl Maint::Database::Upgrade
  8. Clear cache: bin/otrs.Console.pl Maint::Cache::Delete
Caveat Review OTRS 7.0.35 and 8.0.23 release notes for any configuration or feature changes that may require adjustments

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

Fix this in Otrs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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