Owncloud Desktop ClientApplication · Owncloud
CVE-2015-7298
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 · uneditedownCloud Desktop Client before 2.0.1, when compiled with a Qt release after 5.3.x, does not call QNetworkReply::ignoreSslErrors with the list of errors to be ignored, which makes it easier for remote attackers to conduct man-in-the-middle (MITM) attacks by leveraging a server using a self-signed certificate. NOTE: this vulnerability exists because of a partial CVE-2015-4456 regression.
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 confidenceThe ownCloud Desktop Client before version 2.0.1, when compiled with Qt releases after 5.3.x, fails to properly invoke QNetworkReply::ignoreSslErrors with the specific list of SSL errors to be ignored. This causes the client to not validate SSL certificates correctly, allowing man-in-the-middle attackers to exploit self-signed certificates. This is a regression of CVE-2015-4456.
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 Desktop ClientApplication
<= 2.0.0= 5.3.0= 5.4.1CVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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.
-
Determine ownCloud Desktop Client versionOpen the ownCloud Desktop Client, go to Help > About, or run: owncloud --version from command line. On Windows check: C:\Program Files\ownCloud\owncloud.exe version info. On Linux check: owncloud --version or dpkg -l owncloud-clientAffected if Version is 2.0.0 or lower (1.x releases)
-
Identify Qt library version linked to ownCloudOn Linux: ldd $(which owncloud) | grep -i qt or readelf -d owncloud | grep -i qt. On Windows: use a tool like Dependency Walker or dumpbin /dependents on owncloud.exe to list linked Qt librariesAffected if Qt version is 5.3.0, 5.4.1, or any version after 5.3.x (5.4.0 and later)
-
Verify SSL certificate validation behaviorConfigure ownCloud to connect to a server with a self-signed certificate. Monitor network traffic using Wireshark or sslyze. Attempt a connection and observe whether the client accepts the certificate without user warning or proceeds despite SSL errorsAffected if Client connects without warning about untrusted certificates, or ignores SSL certificate errors that should normally prompt a warning
-
Check client configuration for SSL strictnessExamine ownCloud config files: Linux: ~/.local/share/owncloud/owncloud.cfg or /etc/owncloud/client.cfg. Windows: %APPDATA%\owncloud\owncloud.cfg. Look for entries like 'sslStrict' or 'sslNoVerify' set to trueAffected if SSL verification is explicitly disabled via configuration (sslNoVerify=true)
You are affected if ownCloud Desktop Client version is 2.0.0 or lower AND it was compiled with Qt 5.3.0, 5.4.1, or any Qt version after 5.3.x, and SSL certificate validation can be bypassed without proper warnings.
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 Desktop Client to version 2.0.1 or later, which contains the corrected SSL error handling implementation. If immediate upgrade is not possible, ensure users are warned about connecting only over trusted networks.
Fix this in Owncloud Desktop Client
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7298 — 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-2015-7298 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