dbcve.org
OtrsApplication

CVE-2023-38060

HIGH · 8.8 CVSS v3.1 Published 2023-07-24
Fix available
A fix is available. Upgrade to 7.0.45 / 8.0.35 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Improper Input Validation vulnerability in the ContentType parameter for attachments on TicketCreate or TicketUpdate operations of the OTRS Generic Interface modules allows any authenticated attacker to to perform an host header injection for the ContentType header of the attachment.  This issue affects OTRS: from 7.0.X before 7.0.45, from 8.0.X before 8.0.35; ((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

Improper input validation in the ContentType parameter for attachments in OTRS Generic Interface's TicketCreate/TicketUpdate operations allows any authenticated attacker to inject arbitrary values into the ContentType HTTP header. This host header injection can potentially enable HTTP response splitting, cache poisoning, or cross-site scripting (XSS) attacks.

MitigationApply the vendor patches (OTRS 7.0.45, 8.0.35, or Community Edition 6.0.35) to fix the input validation, and validate that attachment ContentType headers are properly sanitized and limited to valid MIME types.

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:>= 6.0.1, <= 6.0.34>= 7.0.0, < 7.0.45>= 8.0.0, < 8.0.35

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

CVSS:3.1/AV:N/AC:L/PR:L/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 OTRS installation and version
    Check the OTRS version file or login to the OTRS admin interface to view the installed version. Common locations include /opt/otrs/RELEASE file or the Admin > System Administration > System Information page.
    Affected if The installed version falls within the affected ranges: 6.0.1 to 6.0.34, 7.0.0 to 7.0.44, or 8.0.0 to 8.0.34.
  2. Verify Generic Interface module is active
    Access OTRS Admin > Generic Interface > Web Service and check if any web services are configured. The vulnerability affects the TicketCreate and TicketUpdate operations within Generic Interface.
    Affected if Generic Interface web services using TicketCreate or TicketUpdate operations are configured and accessible to authenticated users.
  3. Confirm authenticated access to Generic Interface
    Review user permissions and web service configuration to determine if low-privilege or external authenticated users can invoke TicketCreate or TicketUpdate operations via the Generic Interface API.
    Affected if Authenticated attackers can submit requests through the Generic Interface to create or update tickets with attachments.
  4. Check for attachment handling in web service configurations
    Inspect the Generic Interface web service configuration for TicketCreate and TicketUpdate operations to see if attachment handling with customizable ContentType is enabled.
    Affected if The operations accept attachment parameters that allow setting custom ContentType values.

You are affected if you run a vulnerable OTRS version (6.0.1-6.0.34, 7.0.0-7.0.44, or 8.0.0-8.0.34) AND have Generic Interface web services with TicketCreate/TicketUpdate operations accessible to authenticated users who can submit attachments with arbitrary ContentType headers.

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.45 / 8.0.35 or later
Fixed in 7.0.458.0.35
Interim mitigation

Apply the vendor patches (OTRS 7.0.45, 8.0.35, or Community Edition 6.0.35) to fix the input validation, and validate that attachment ContentType headers are properly sanitized and limited to valid MIME types.

Recommended fix High confidence

OTRS 6.0.35+ (Community Edition), OTRS 7.0.45+, or OTRS 8.0.35+ depending on your current branch

  1. 1. Identify the currently installed OTRS version by checking the version file or admin interface.
  2. 2. For OTRS 6.0.x (Community Edition): Upgrade to version 6.0.35 or later.
  3. 3. For OTRS 7.0.x: Upgrade to version 7.0.45 or later.
  4. 4. For OTRS 8.0.x: Upgrade to version 8.0.35 or later.
  5. 5. After upgrading, verify the Generic Interface configuration to ensure the fix is applied.
  6. 6. Test TicketCreate and TicketUpdate operations with attachments to confirm the vulnerability is remediated.
Caveat Review OTRS upgrade documentation for your specific version path as minor version upgrades may include configuration or dependency changes; test in 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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-2023-38060 — 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-2023-38060 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