dbcve.org
Debian LinuxOperating system · Debian

CVE-2019-9892

MEDIUM · 6.5 CVSS v3.1 Published 2019-05-22
Fix available
A fix is available. Upgrade to after 7.0.6 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
An issue was discovered in Open Ticket Request System (OTRS) 5.x through 5.0.34, 6.x through 6.0.17, and 7.x through 7.0.6. An attacker who is logged into OTRS as an agent user with appropriate permissions may try to import carefully crafted Report Statistics XML that will result in reading of arbitrary files on the OTRS filesystem.

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

This is an XML parsing vulnerability in OTRS Report Statistics XML import functionality. An authenticated agent with appropriate permissions can import a maliciously crafted XML file that triggers arbitrary file read on the OTRS server filesystem, likely through XML external entity (XXE) injection.

MitigationUpgrade to OTRS 5.0.35, 6.0.18, or 7.0.7 or later to patch the vulnerability. Until patched, restrict the Report Statistics import permission to only necessary users and monitor for suspicious XML imports.

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
Debian LinuxOperating system
Affected:= 8.0
OtrsApplication
Affected:>= 5.0.0, <= 5.0.34>= 6.0.0, <= 6.0.17>= 7.0.0, <= 7.0.6

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if OTRS is installed
    Look for OTRS installation directories (e.g., /opt/otrs, /var/www/otrs) or check for OTRS web application responding on the server. Also check for OTRS processes running.
    Affected if OTRS is present on the server
  2. Determine the installed OTRS version
    Check the OTRS version file (e.g., /opt/otrs/Kernel/OTRSVersion.pm) or log into the OTRS admin interface and navigate to Admin > System Administration > System Information. Compare the version against the affected ranges: 5.0.0-5.0.34, 6.0.0-6.0.17, or 7.0.0-7.0.6.
    Affected if The installed version falls within 5.0.0 to 5.0.34, 6.0.0 to 6.0.17, or 7.0.0 to 7.0.6
  3. Check if Report Statistics module is enabled
    Log into OTRS as an admin and navigate to Admin > Role Management or Group Management. Verify if any roles or groups have access to the 'Report Statistics' module (often labeled as 'Importing statistics' or similar XML import permissions).
    Affected if The Report Statistics import functionality is accessible to any authenticated agent
  4. Identify users with XML import permissions
    In Admin > User Management and Admin > Role Management, review which users or roles are assigned permissions that include 'Import statistics' or Report Statistics XML import capability.
    Affected if Any user account (other than admin) has permission to import Report Statistics XML files
  5. Audit logs for XML import activity
    Check OTRS system logs (typically in /opt/otrs/var/log/ or via the web interface at Admin > System Log) for recent entries containing 'Import', 'Statistics', or 'XML' to identify any recent XML import operations.
    Affected if Suspicious or unexpected XML import events are found in the logs

A user is affected if OTRS version 5.0.0-5.0.34, 6.0.0-6.0.17, or 7.0.0-7.0.6 is installed AND the Report Statistics XML import feature is enabled for any authenticated agent.

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.

From vendor data
Upgrade available Upgrade to a release after 7.0.6
Interim mitigation

Upgrade to OTRS 5.0.35, 6.0.18, or 7.0.7 or later to patch the vulnerability. Until patched, restrict the Report Statistics import permission to only necessary users and monitor for suspicious XML imports.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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