Debian LinuxOperating system · Debian
CVE-2017-15864
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 · uneditedIn the Agent Frontend in Open Ticket Request System (OTRS) 3.3.x through 3.3.18, with a crafted URL it is possible to gain information like database user and password.
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 confidenceA URL handling vulnerability in the OTRS Agent Frontend (versions 3.3.x through 3.3.18) allows unauthenticated attackers to craft malicious URLs that expose sensitive database credentials including usernames and passwords in error messages or responses.
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
= 7.0= 8.0= 9.0>= 3.3.0, <= 3.3.18CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm OTRS installationLocate the OTRS installation by checking common directories such as /opt/otrs, /var/www/otrs, or via package manager (dpkg -l | grep otrs on Debian-based systems).Affected if OTRS software is found on the system
-
Identify installed OTRS versionExamine the version file within the OTRS installation directory, typically found in Kernel/Version.pm or by running the OTRS version command if available in the bin directory.Affected if The installed version falls within the range 3.3.0 through 3.3.18 inclusive
-
Verify Agent Frontend is accessibleDetermine if the OTRS web interface (typically accessed via /otrs/index.pl or similar path) is exposed by checking web server configuration files (Apache, Nginx) and testing network connectivity to port 80/443.Affected if The Agent Frontend web interface is reachable from the network (including untrusted networks)
-
Test for credential exposure in URL error responsesSend a crafted request to the Agent Frontend with malformed URL parameters and observe whether database credentials, usernames, or passwords appear in error messages or responses.Affected if Sensitive database credentials are visible in error messages when handling malformed URLs
The system is affected if OTRS version 3.3.0 through 3.3.18 is installed and the Agent Frontend web interface is network-accessible, allowing unauthenticated attackers to trigger error messages containing database credentials.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade OTRS to version 3.3.18 or later (preferably the latest supported release) to patch the vulnerability. Alternatively, restrict access to the Agent Frontend via network-level controls until the upgrade can be performed.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15864 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-15864 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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