dbcve.org
Calendar Resource PlanningApplication · Otrs

CVE-2022-32739

MEDIUM · 5.3 CVSS v3.1 Published 2022-06-13
Fix available
A fix is available. Upgrade to 7.0.31 / 7.0.35 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
When Secure::DisableBanner system configuration has been disabled and agent shares his calendar via public URL, received ICS file contains OTRS release number.

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

This is an information disclosure vulnerability in OTRS where the software release number is leaked into ICS calendar files when shared via public URL. When the Secure::DisableBanner system configuration is disabled, the ICS export includes the OTRS version information, which could aid attackers in reconnaissance to identify specific vulnerable versions.

MitigationEnable the Secure::DisableBanner system configuration setting to prevent release number disclosure, or apply vendor patch to modify ICS generation to exclude version information from calendar exports.

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
Calendar Resource PlanningApplication
Affected:>= 7.0.0, < 7.0.31>= 8.0.0, < 8.0.23
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 installed OTRS version
    Access the admin panel and navigate to 'Admin' > 'System Administration' > 'System Information' or check the kernel/VERSION.pm file in the OTRS installation directory. Alternatively, run: grep -r 'VERSION' /opt/otrs/Kernel/VERSION.pm 2>/dev/null or check the About page in the web interface.
    Affected if The installed version is 7.0.0 through 7.0.34, 7.0.36 through 7.0.39 (for Otrs), 7.0.0 through 7.0.30 (for Otrs Calendar Resource Planning), 8.0.0 through 8.0.22, or any 8.0.x version before 8.0.23 for either product.
  2. Verify Secure::DisableBanner configuration
    In the OTRS admin interface, go to 'Admin' > 'System Administration' > 'System Configuration' and search for 'Secure::DisableBanner'. Alternatively, check the Config.pm file or export the configuration setting using the admin console command: /opt/otrs/bin/otrs.Console.pl Admin::Config::List --filter Secure::DisableBanner
    Affected if The Secure::DisableBanner setting is set to 'No', 'False', or is unset (default), indicating the version banner is displayed in ICS exports.
  3. Test ICS calendar export for version leakage
    Generate a public calendar export URL for any calendar event or resource. Export the calendar as ICS format using the public share feature. Open the exported .ics file in a text editor and search for 'OTRS', 'Version', or product name strings.
    Affected if The ICS file contains comments, headers, or fields that reveal the OTRS version number (such as X-Generated-By: OTRS 7.x.x or similar version disclosure).

You are affected if your OTRS version falls within the vulnerable ranges AND the Secure::DisableBanner setting is disabled or unset, AND your ICS calendar exports contain version information that could aid reconnaissance.

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

Enable the Secure::DisableBanner system configuration setting to prevent release number disclosure, or apply vendor patch to modify ICS generation to exclude version information from calendar exports.

Recommended fix High confidence

OTRS 7.0.x → 7.0.35 | OTRS 8.0.x → 8.0.23 | Calendar Resource Planning 7.0.x → 7.0.31 | Calendar Resource Planning 8.0.x → 8.0.23

  1. 1. Identify the currently installed OTRS or Calendar Resource Planning version using the admin dashboard or system information.
  2. 2. For OTRS 7.0.x users: Upgrade to OTRS 7.0.35 or later.
  3. 3. For OTRS 8.0.x users: Upgrade to OTRS 8.0.23 or later.
  4. 4. For Calendar Resource Planning 7.0.x users: Upgrade to version 7.0.31 or later.
  5. 5. For Calendar Resource Planning 8.0.x users: Upgrade to version 8.0.23 or later.
  6. 6. After upgrade, verify the fix by generating a public calendar URL and exporting the ICS file to confirm no version information is included.
  7. 7. Optionally, re-enable the Secure::DisableBanner configuration if it was previously disabled.

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

Fix this in Calendar Resource Planning Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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