# CVE-2015-4456: Security feature bypass in n/a

> Man-in-the-middle attackers can bypass certificate distrust decisions in the ownCloud Desktop Client to obtain sensitive information via self-signed certificates.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-4456, DSA-3363-1, GHSA-p85q-834g-x9vx, MGASA-2015-0256

## What is CVE-2015-4456?

CVE-2015-4456 is a low-severity vulnerability in n/a, published on 26 Oct 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

ownCloud Desktop Client before 1.8.2 does not call QNetworkReply::ignoreSslErrors with the list of errors to be ignored, which allows man-in-the-middle attackers to bypass the user's certificate distrust decision and obtain sensitive information by leveraging a self-signed certificate and a connection to a server using its own self-signed certificate.

## Which versions are affected by CVE-2015-4456?

It affects 1 product.


Products: Owncloud Owncloud Desktop Client.

## How do I fix CVE-2015-4456?

Upgrade to a fixed version.

## Is CVE-2015-4456 being exploited?

There is no known exploitation of CVE-2015-4456 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2016-7102](https://insights.sbomify.com/CVE-2016-7102/): Code injection in n/a (high 8.4)
- [CVE-2020-28646](https://insights.sbomify.com/CVE-2020-28646/): Code injection in n/a (high 7.8)
- [CVE-2015-7298](https://insights.sbomify.com/CVE-2015-7298/): Security feature bypass in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4456 and fix it if it is affected.

What it is: CVE-2015-4456 is a low-severity vulnerability in n/a, published on 26 Oct 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-4456 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-4456/ (Markdown: https://insights.sbomify.com/CVE-2015-4456/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-4456
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-4456
- OSV: https://osv.dev/vulnerability/CVE-2015-4456

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-4456/
Summaries are generated and may contain mistakes; the official description above is the record.