CVE-2017-14754
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 · uneditedOpenText Document Sciences xPression (formerly EMC Document Sciences xPression) v4.5SP1 Patch 13 (older versions might be affected as well) is prone to Arbitrary File Read: /xAdmin/html/cm_datasource_group_xsd.jsp, parameter: xsd_datasource_schema_file filename. In order for this vulnerability to be exploited, an attacker must authenticate to the application first.
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 confidenceOpenText Document Sciences xPression contains an arbitrary file read vulnerability in /xAdmin/html/cm_datasource_group_xsd.jsp via the xsd_datasource_schema_file parameter, allowing authenticated attackers to read arbitrary files from the server filesystem through path traversal.
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<= 4.5CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm OpenText Document Sciences xPression is installedLocate the xPression application installation directory or identify the running service. Check for the presence of the /xAdmin/ web application path in the web server configuration.Affected if The application is installed and the /xAdmin/ administrative interface is accessible on the server.
-
Check the installed xPression versionIdentify the installed version of Document Sciences xPression from the application documentation, installation files, or version information displayed in the administrative interface. Compare it against the affected range of <= 4.5.Affected if The installed version is 4.5 or lower.
-
Verify the vulnerable JSP endpoint is reachableConfirm that the /xAdmin/html/cm_datasource_group_xsd.jsp file exists and is accessible via HTTP/HTTPS on the server.Affected if The endpoint responds to requests, indicating the vulnerable component is present.
-
Confirm authentication is required for the administrative interfaceDetermine whether the /xAdmin/ interface enforces authentication. Check if an attacker with valid credentials could access the vulnerable endpoint.Affected if The /xAdmin/ interface permits authenticated access, allowing the path traversal via the xsd_datasource_schema_file parameter.
A user is affected if OpenText Document Sciences xPression version 4.5 or lower is installed, the /xAdmin/html/cm_datasource_group_xsd.jsp endpoint is accessible, and an attacker can authenticate to the administrative interface to exploit the path traversal vulnerability.
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 dataApply vendor patches when available, or implement strict input validation on the xsd_datasource_schema_file parameter to prevent directory traversal sequences; consider restricting access to the /xAdmin/ administrative interface to trusted networks only.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14754 — 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-14754 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