dbcve.org
OtrsApplication

CVE-2024-23791

HIGH · 7.5 CVSS v3.1 Published 2024-01-29
Fix available
A fix is available. Upgrade to 7.0.49 / 2024.1.1 or later.
See remediation →
84/100
Remediation priority · High
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
Insertion of debug information into log file during building the elastic search index allows reading of sensitive information from articles.This issue affects OTRS: from 7.0.X through 7.0.48, from 8.0.X through 8.0.37, from 2023.X through 2023.1.1.

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

During the elastic search index building process in OTRS, debug information containing sensitive article data is being written to log files. This allows unauthorized users with access to these logs to read sensitive information from articles.

MitigationUpgrade OTRS to version 7.0.49+, 8.0.38+, or 2023.2+ to patch the debug logging vulnerability, or restrict access to log files if immediate patching is not feasible.

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.49>= 8.0.0, < 2024.1.1

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

CVSS:3.1/AV:N/AC:L/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 OTRS version
    Check the OTRS version by accessing the admin panel or examining the version file in the OTRS installation directory.
    Affected if The installed version falls within 7.0.0 to 7.0.48, or 8.0.0 to 2024.1.0, indicating the vulnerability is present.
  2. Verify if Elasticsearch module is enabled
    Check the OTRS system configuration to determine whether the Elasticsearch indexing feature is active. This is typically found in the admin settings or configuration files.
    Affected if Elasticsearch index building is enabled and the OTRS version is within the affected ranges.
  3. Examine log files for sensitive article data
    Review OTRS log files in the log directory for entries containing sensitive article contents, customer data, or communication details that should not appear in logs.
    Affected if Log files contain plaintext sensitive information from articles, confirming the vulnerability has been triggered and data has been exposed.
  4. Check log file access controls
    Verify who has read access to the OTRS log directories and files.
    Affected if Log files are accessible to unauthorized users, which would allow them to read any sensitive debug data written during Elasticsearch index building.

A user is affected if they run OTRS version 7.0.0-7.0.48 or 8.0.0-2024.1.0 with Elasticsearch enabled, and log files contain sensitive article data.

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.49 / 2024.1.1 or later
Fixed in 7.0.492024.1.1
Interim mitigation

Upgrade OTRS to version 7.0.49+, 8.0.38+, or 2023.2+ to patch the debug logging vulnerability, or restrict access to log files if immediate patching is not feasible.

Recommended fix High confidence

OTRS 7.0.49 or OTRS 2024.1.1 (depending on your major version branch)

  1. 1. Backup your current OTRS installation and database before proceeding.
  2. 2. Identify your current OTRS version by checking the version file or admin interface.
  3. 3. For OTRS 7.0.x versions (7.0.0 through 7.0.48): Upgrade to OTRS 7.0.49 or later.
  4. 4. For OTRS 8.0.x versions (8.0.0 through 8.0.37): Upgrade to OTRS 2024.1.1 or later.
  5. 5. For OTRS 2023.x versions (2023.x through 2023.1.1): Upgrade to OTRS 2024.1.1 or later.
  6. 6. After upgrade, verify the fix by checking that debug information is no longer being written to log files during Elasticsearch index building.
  7. 7. Review log files to confirm no sensitive information from articles was previously exposed.
Caveat Review OTRS upgrade documentation for your specific version path as there may be migration requirements between major versions

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

Fix this in Otrs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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