dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-23793

MEDIUM · 6.3 CVSS v3.1 Published 2024-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable

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
The file upload feature in OTRS and ((OTRS)) Community Edition has a path traversal vulnerability. This issue permits authenticated agents or customer users to upload potentially harmful files to directories accessible by the web server, potentially leading to the execution of local code like Perl scripts. This issue affects OTRS: from 7.0.X through 7.0.49, 8.0.X, 2023.X, from 2024.X through 2024.3.2; ((OTRS)) Community Edition: from 6.0.1 through 6.0.34.

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

Path traversal vulnerability in OTRS/((OTRS)) Community Edition file upload feature allows authenticated agents or customer users to upload files to arbitrary directories accessible by the web server, potentially enabling remote code execution via malicious Perl scripts.

MitigationUpgrade to OTRS 7.0.50, 8.0.7, 2024.4+ or ((OTRS)) CE 6.0.35+. Alternatively, implement strict input validation on file path parameters and restrict upload directories to non-executable locations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L

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 installation and version
    Check the OTRS version by examining the Kernel/Config.pm file or running 'otrs.Console.pl Admin::Package::List' in the OTRS home directory. Also check Kernel/VERSION.pm if it exists.
    Affected if The installed version is OTRS 7.0.x below 7.0.50, 8.0.x below 8.0.7, 2024.x below 2024.4, or ((OTRS)) CE 6.0.x below 6.0.35.
  2. Verify file upload feature is accessible
    Check the OTRS system configuration under 'Ticket::Article::Backend::MIMEEntity::ArticleAttachment' or review the SysConfig settings for 'Ticket::Article::Backend::MIMEEntity::ArticleAttachmentStore' to confirm the attachment storage feature is enabled.
    Affected if The file upload/attachment storage feature is enabled and accessible to agents or customer users.
  3. Check upload directory configuration
    Inspect the SysConfig setting 'UploadDir' under 'Ticket::Article::Backend::MIMEEntity' or check Kernel/Config.pm for the $Self->{'UploadDir'} parameter to identify the configured upload directory path.
    Affected if The upload directory is not restricted to a non-executable location or allows path traversal in the file naming.
  4. Confirm agent/customer user permissions
    Review the role and group permissions in OTRS admin panel to determine if standard agents or customer users have the ability to create or upload articles with attachments.
    Affected if Authenticated agents or customer users have permission to upload files via the ticket article attachment feature.

You are affected if OTRS is installed with a version prior to 7.0.50, 8.0.7, 2024.4, or ((OTRS)) CE 6.0.35 AND the file attachment upload feature is enabled for agents or customer users.

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 to OTRS 7.0.50, 8.0.7, 2024.4+ or ((OTRS)) CE 6.0.35+. Alternatively, implement strict input validation on file path parameters and restrict upload directories to non-executable locations.

Recommended fix Moderate confidence

Upgrade to OTRS 7.0.50+, 8.0.x latest patch, 2024.3.3+, or ((OTRS)) Community Edition 6.0.35+

  1. 1. Identify your current OTRS or ((OTRS)) Community Edition version by checking the admin panel or running 'perl bin/otrs.Console.pl Admin::Package::List'
  2. 2. Determine the appropriate upgrade path based on your current version branch
  3. 3. Backup your OTRS database and configuration files before proceeding
  4. 4. Download the latest patch version for your respective branch from the official OTRS download page (https://otrs.com/download)
  5. 5. Stop the OTRS web server (e.g., Apache/Nginx)
  6. 6. Install the upgrade following the OTRS upgrade guide for your version
  7. 7. Start the OTRS web server
  8. 8. Verify the installation by logging in and checking the system information
Caveat Review OTRS release notes for breaking changes between your current version and target version before upgrading; test thoroughly in staging environment

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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