dbcve.org
OwncloudApplication

CVE-2015-4718

HIGH · 9.0 CVSS v2.0 Published 2015-10-21
Fix available
A fix is available. Upgrade to after 6.0.7 or later.
See remediation →
96/100
Remediation priority · Urgent
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
The external SMB storage driver in ownCloud Server before 6.0.8, 7.0.x before 7.0.6, and 8.0.x before 8.0.4 allows remote authenticated users to execute arbitrary SMB commands via a ; (semicolon) character in a file.

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

The external SMB storage driver in ownCloud does not properly sanitize filenames before passing them to SMB commands. A remote authenticated user can inject arbitrary SMB commands by including a semicolon (;) character in a file name, which acts as a command separator.

MitigationUpgrade to ownCloud Server 6.0.8, 7.0.6, 8.0.4 or later. As a compensating control, restrict SMB storage access to trusted users only until patching is complete.

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
OwncloudApplication
Affected:<= 6.0.7
Owncloud ServerApplication
Affected:= 7.0.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 8.0.0= 8.0.2= 8.0.3

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
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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 ownCloud version
    Check the version.php file in the ownCloud root directory, typically at version.php or lib/version.php. Alternatively, check the ownCloud admin panel under the admin page which displays the current version.
    Affected if The installed version is <= 6.0.7, or one of 7.0.0 through 7.0.5, 8.0.0, 8.0.2, or 8.0.3
  2. Confirm SMB external storage is enabled
    Navigate to ownCloud admin settings and check if the 'External storage support' app or feature is enabled. This is typically found under Apps > External storage, or in the admin panel under Storage section.
    Affected if External storage support is enabled and SMB storage backends are available
  3. Review configured SMB storage mounts
    Check the ownCloud database table oc_external_config or config.php for external storage mounts with type 'smb'. In the admin UI, go to Settings > External Storage to list any SMB shares that are configured.
    Affected if There are SMB external storage mounts configured and enabled for any users
  4. Inspect file names in SMB storage for injection attempts
    Examine the files stored on the SMB backend for file names containing semicolon characters (;) or other shell metacharacters. Use SMB client tools like smbclient to list files on the configured share.
    Affected if Any file names in the SMB share contain semicolons or appear to be attempting command injection

You are affected if your ownCloud version matches the vulnerable versions listed AND SMB external storage is enabled with at least one SMB mount configured.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.0.7
Interim mitigation

Upgrade to ownCloud Server 6.0.8, 7.0.6, 8.0.4 or later. As a compensating control, restrict SMB storage access to trusted users only until patching is complete.

Recommended fix High confidence

ownCloud Server 7.0.6 (or later), or ownCloud 6.0.8 (or later), or ownCloud Server 8.0.4 (or later)

  1. Upgrade ownCloud Server to version 7.0.6 or later to remediate the SMB command injection vulnerability
  2. If running ownCloud (not Server), upgrade to version 6.0.8 or later
  3. If running 8.0.x branch, upgrade to version 8.0.4 or later (per official description)
  4. After upgrade, verify that the external SMB storage functionality works correctly
Caveat Review ownCloud upgrade documentation for breaking changes between 7.0.x and 7.0.6; ensure PHP and database compatibility with target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Owncloud Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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