dbcve.org
OtrsApplication

CVE-2024-23792

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 adding attachments to ticket comments, another user can add attachments as well impersonating the orginal user. The attack requires a logged-in other user to know the UUID. While the legitimate user completes the comment, the malicious user can add more files to the comment. 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

In OTRS, when a user creates a ticket comment with attachments, another logged-in user who knows the UUID of the in-progress comment can add unauthorized attachments to that comment. This is a race condition/authorization bypass where the system does not properly validate that the user adding attachments is the same user who initiated the comment.

MitigationUpgrade OTRS to version 7.0.49, 8.0.38, or 2023.2.0 or later which contain the security fix for proper authorization validation on attachment operations.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 the installed OTRS version
    Locate the OTRS version file (typically in /opt/otrs/RELEASE or via the admin panel under 'System Administration > System Information'), or run: perl -I/opt/otrs -MOTRS= -e 'print $OTRS::Version::String . " "'
    Affected if The version is 7.0.0 through 7.0.48, or 8.0.0 through 2024.1.0 (i.e., it falls within >= 7.0.0 < 7.0.49 or >= 8.0.0 < 2024.1.1)
  2. Determine if ticket comments with attachments are created
    Query the OTRS database (table article, column article_type_id) or use the admin interface to search for ticket articles that contain attachments, or inspect /opt/otrs/var/log/ for attachment-related operations
    Affected if The system stores or processes ticket comments that include file attachments - this is the feature the vulnerability exploits
  3. Review application logs for unauthorized attachment operations
    Examine OTRS logs in /opt/otrs/var/log/ (especially Core.log or Apache/error.log) for attachment upload operations, focusing on whether the user performing the upload matches the user who created the comment. Search for patterns involving 'Attachment' and 'Article' with mismatched UserID values
    Affected if Logs show attachment operations on ticket comments performed by users who did not initiate those comments, or multiple UserIDs accessing the same comment/attachment UUID in short succession

You are affected if your OTRS version is within the vulnerable range AND your system allows ticket comments with attachments AND there is evidence of unauthorized attachment modifications or anomalous UUID-based access patterns in your logs.

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.0 or later which contain the security fix for proper authorization validation on attachment operations.

Recommended fix High confidence

Upgrade to OTRS 7.0.49 or 2024.1.1 depending on your major version branch

  1. 1. Back up your current OTRS database and configuration files before upgrading.
  2. 2. Download OTRS version 7.0.49 (for 7.x installations) or version 2024.1.1 (for 8.x installations) from the official OTRS website (otrs.com).
  3. 3. Stop the OTRS services to ensure no active sessions during the upgrade process.
  4. 4. Install the new version following the official OTRS upgrade documentation.
  5. 5. Verify the upgrade was successful by logging in and testing the attachment functionality in ticket comments.
  6. 6. Confirm that the UUID-based attachment hijacking vulnerability is no longer present.
Caveat Review OTRS upgrade notes for any changes in functionality or configuration requirements between your current version and the target version

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

Fix this in Otrs Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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