dbcve.org
OtrsApplication

CVE-2022-4427

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-19
Fix available
A fix is available. Upgrade to 7.0.40 / 8.0.28 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 OTRS AG OTRS, OTRS AG ((OTRS)) Community Edition allows SQL Injection via TicketSearch Webservice This issue affects OTRS: from 7.0.1 before 7.0.40 Patch 1, from 8.0.1 before 8.0.28 Patch 1; ((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

SQL injection vulnerability in OTRS and OTRS Community Edition's TicketSearch web service allows attackers to inject malicious SQL queries through improper input validation. This critical flaw enables unauthorized database access, potentially exposing sensitive customer data, ticket information, and authentication credentials.

MitigationApply vendor patches by upgrading to OTRS 7.0.40 Patch 1+, 8.0.28 Patch 1+, or the patched Community Edition version. Alternatively, implement strict input validation on all TicketSearch web service parameters at the application or WAF layer until patching is 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:>= 6.0.1, <= 6.0.34>= 7.0.1, < 7.0.40>= 8.0.1, < 8.0.28= 7.0.40= 8.0.28

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. Determine installed OTRS version
    Access the OTRS admin panel under Admin > System Information, or check the version file in the OTRS installation directory (typically VERSION or RELEASE file in the root directory). Compare the version number to the affected ranges: 6.0.1 through 6.0.34, 7.0.1 through 7.0.40, 8.0.1 through 8.0.28.
    Affected if The installed version falls within any of these ranges: >= 6.0.1 and <= 6.0.34; >= 7.0.1 and < 7.0.40; >= 8.0.1 and < 8.0.28; or equals exactly 7.0.40 or 8.0.28.
  2. Identify if TicketSearch web service is configured
    Access the OTRS admin panel and navigate to Admin > Web Services to review all configured web services. Locate any web service that exposes the TicketSearch operation.
    Affected if A web service exposing the TicketSearch operation is present and active in the OTRS system.
  3. Verify TicketSearch web service input handling
    Inspect the web service configuration file (typically stored in Kernel/Config/Files or via the web service admin interface) to examine how the TicketSearch operation handles input parameters.
    Affected if The TicketSearch web service configuration lacks proper input validation or parameter sanitization on search fields.
  4. Review web service permission settings
    Check the web service ACL (Access Control List) or permission configuration to determine which user roles can invoke the TicketSearch operation.
    Affected if The TicketSearch web service is accessible to unauthenticated or low-privilege users without restricted parameter constraints.

You are affected if your OTRS version is within the affected ranges AND the TicketSearch web service is configured and accessible without strict input validation.

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.40 / 8.0.28 or later
Fixed in 7.0.408.0.28
Interim mitigation

Apply vendor patches by upgrading to OTRS 7.0.40 Patch 1+, 8.0.28 Patch 1+, or the patched Community Edition version. Alternatively, implement strict input validation on all TicketSearch web service parameters at the application or WAF layer until patching is feasible.

Recommended fix High confidence

OTRS 7.0.40 Patch 1+ (for 7.x), OTRS 8.0.28 Patch 1+ (for 8.x), OTRS 6.0.35+ (for Community Edition 6.x)

  1. 1. Back up your OTRS database and configuration files before proceeding.
  2. 2. Identify your current OTRS version by checking the admin interface or running: bin/otrs.Console.pl Admin::Package::List
  3. 3. For OTRS 7.x (versions 7.0.1 to 7.0.39): Upgrade to OTRS 7.0.40 Patch 1 or later.
  4. 4. For OTRS 8.x (versions 8.0.1 to 8.0.27): Upgrade to OTRS 8.0.28 Patch 1 or later.
  5. 5. For OTRS Community Edition 6.x (versions 6.0.1 to 6.0.34): Upgrade to OTRS 6.0.35 or later.
  6. 6. Download the appropriate package from the official OTRS downloads page (otrs.com).
  7. 7. Stop the OTRS service: bin/otrs.StopService.pl
  8. 8. Run the upgrade installer following OTRS upgrade documentation.
Caveat Review OTRS release notes for breaking changes between your current version and target version; major version upgrades may require migration steps

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

Fix this in Otrs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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