Owncloud ServerApplication · Owncloud
CVE-2014-2056
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 · uneditedPHPDocX, as used in ownCloud Server before 5.0.15 and 6.0.x before 6.0.2, allows remote attackers to read arbitrary files, cause a denial of service, or possibly have other impact via an XML External Entity (XXE) attack.
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 confidencePHPDocX library as used in ownCloud Server fails to properly disable external entity processing in XML parsing, allowing remote attackers to inject malicious XML that references external entities. This enables disclosure of local file contents, denial of service via resource exhaustion, and potential further compromise.
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
Owncloud ServerApplication
<= 5.0.14= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.10all versionsCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check ownCloud Server versionLocate the ownCloud version file (typically version.php in the config directory) or access the ownCloud admin panel to view the installed version numberAffected if The installed version is 5.0.14 or any version from 5.0.0 through 5.0.10 inclusive, as listed in the affected versions range
-
Identify PHPDocX library presenceSearch for the PHPDocX library files in the ownCloud installation directory, typically under 3rdparty or lib/vendor foldersAffected if The PHPDocX library directory exists in the ownCloud installation
-
Verify document processing feature usageDetermine if ownCloud document conversion or Word document handling features are enabled or actively used (check admin settings for apps like Documents or the files which may process .docx files)Affected if Document processing features that leverage PHPDocX are enabled or users upload/process .docx files
-
Inspect XML parser configurationReview PHP configuration and any custom XML parsing code within ownCloud that utilizes the PHPDocX library to see if external entity processing is explicitly disabledAffected if The XML parser is configured to allow external entity processing (XXE is not mitigated)
You are affected if your ownCloud Server version is 5.0.14 or lower AND the PHPDocX library is present with document processing features enabled, as this combination enables the XXE vulnerability in XML parsing.
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 ownCloud Server to version 5.0.15 or 6.0.2 or later which includes the patched PHPDocX library with XXE protection enabled.
Fix this in Owncloud Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2056 — 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-2014-2056 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