dbcve.org
OtrsApplication

CVE-2024-23790

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
Improper Input Validation vulnerability in the upload functionality for user avatars allows functionality misuse due to missing check of filetypes. This issue affects OTRS: from 7.0.X through 7.0.48, from 8.0.X through 8.0.37, from 2023 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 · moderate confidence

Improper input validation in OTRS avatar upload functionality allows users to upload arbitrary file types due to missing file type checks. This could enable attackers to upload malicious files (executables, scripts, web shells) as avatars, potentially leading to remote code execution if these files are accessible via the web server or processed by the application.

MitigationImplement strict file type validation on avatar uploads using a combination of file extension whitelist, MIME type verification, and magic byte/signature validation to ensure only safe image formats (JPG, PNG, GIF) are accepted.

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

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

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
    Check the OTRS version file or admin interface. The version is typically stored in a Version.pm file in the OTRS kernel directory, or can be retrieved via the admin dashboard under 'System Administration > System Information'.
    Affected if The installed version is 7.0.0 through 7.0.48, or 8.0.0 through 2024.1.0 (i.e., any version >= 7.0.0 but < 7.0.49, or >= 8.0.0 but < 2024.1.1).
  2. Verify avatar upload functionality is accessible
    Confirm that user avatar upload is enabled in OTRS. Navigate to 'User Profile' or 'Personal Preferences' as a logged-in user and check if an avatar upload option exists. Alternatively, check the SysConfig under 'Frontend::User::Avatar' for 'AvatarUpload' settings.
    Affected if Avatar upload functionality is enabled and accessible to end users (not restricted to admin-only).
  3. Inspect avatar storage directory
    Locate where OTRS stores uploaded avatars. This is typically configured in SysConfig under 'Frontend::User::Avatar::AvatarStorage' or found in the var/ directory. Check if the storage path is web-accessible (e.g., under the web server document root).
    Affected if Uploaded avatar files are stored in a directory accessible via HTTP/HTTPS (e.g., /otrs/index.pl/Avatar/ or similar web-accessible path).

You are affected if your OTRS version falls within 7.0.0-7.0.48 or 8.0.0-2024.1.0 AND the avatar upload feature is enabled AND uploaded files are served from a web-accessible location, allowing potential remote code execution.

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

Implement strict file type validation on avatar uploads using a combination of file extension whitelist, MIME type verification, and magic byte/signature validation to ensure only safe image formats (JPG, PNG, GIF) are accepted.

Recommended fix High confidence

Upgrade to OTRS 7.0.49+ for 7.x branch, or OTRS 2024.1.1+ for 8.x branch

  1. 1. Determine your current OTRS version by checking the admin panel or running: OTRS/bin/otrs.Console.pl Admin::Config::Read --version
  2. 2. For OTRS 7.0.x versions (7.0.0 through 7.0.48): Upgrade to OTRS 7.0.49 or later
  3. 3. For OTRS 8.0.x versions (8.0.0 through 8.0.37): Upgrade to OTRS 2024.1.1 or later
  4. 4. Download the appropriate upgrade package from the official OTRS download page (https://otrs.com/download/)
  5. 5. Back up your existing OTRS installation and database before performing the upgrade
  6. 6. Follow the OTRS upgrade documentation for your version to complete the upgrade process
  7. 7. Verify the upgrade was successful by checking the version in the admin panel
Caveat Review OTRS upgrade notes for potential breaking changes between versions; test in a non-production environment first

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

Fix this in Otrs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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