Owncloud ServerApplication · Owncloud
CVE-2014-2055
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 · uneditedSabreDAV before 1.7.11, 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 confidenceSabreDAV before 1.7.11 contains an XML External Entity (XXE) vulnerability in its XML parser. By submitting specially crafted XML requests, remote attackers can exploit insufficiently secured XML entity processing to read arbitrary files from the server filesystem, cause denial of service, or potentially execute other impacts.
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
= 6.0.0= 6.0.1<= 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<= 1.7.10= 1.6.0= 1.6.1= 1.6.2= 1.6.3= 1.6.4= 1.6.5= 1.6.6= 1.6.7= 1.6.8= 1.6.9= 1.6.10CVSS 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.
-
Locate SabreDAV or ownCloud installationLook for sabredav directory in web root (commonly /var/www/, /srv/www/, or your webserver's document root), or check for owncloud data directoryAffected if SabreDAV or ownCloud is present on the server
-
Find SabreDAV version fileIn the SabreDAV directory, check for a VERSION, changelog, or composer.json file that states the version. In ownCloud, check version.php in the root or 3rdparty/sabredav folderAffected if Cannot determine version or version is exposed in these files
-
Compare installed version to affected rangesFor SabreDAV: version <= 1.7.10 or between 1.6.0 and 1.6.10. For ownCloud: version 5.0.x up to 5.0.14, or versions 6.0.0/6.0.1Affected if Installed version falls within any of these ranges
-
Verify XML request handling is enabledConfirm the server accepts WebDAV/XML requests (this is the core SabreDAV function). Check that the WebDAV endpoint is accessible and processes PUT/GET requests with XML bodiesAffected if XML request processing is active (default behavior for SabreDAV)
-
Check XML parser configuration for external entity processingReview PHP xml parser settings or any custom XML configuration that may control entity processing. Inspect lib/XmlReader.php or similar XML handling code in the SabreDAV installationAffected if External entity processing is not explicitly disabled in the XML parser configuration
If SabreDAV version <= 1.7.10 or ownCloud 5.0.x <= 5.0.14/6.0.x is installed AND XML request handling is enabled, the server is vulnerable to XXE attacks.
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 SabreDAV to version 1.7.11 or later, or update ownCloud Server to 5.0.15+/6.0.2+ which include the patched SabreDAV version. Alternatively, ensure XML parsers are configured to disable external entity processing.
Fix this in Owncloud Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2055 — 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-2055 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