# CVE-2016-6526: Deserialization in n/a

> Attackers can cause denial of service or gain privileges in Samsung Telecom app via malformed serializable objects.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qfmx-j5pw-rv5p

## What is CVE-2016-6526?

CVE-2016-6526 is a high-severity unsafe deserialization vulnerability in n/a, published on 18 Jan 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The SpamCall Activity component in Telecom application on Samsung Note device L(5.0/5.1) and M(6.0) allows attackers to cause a denial of service (crash and reboot) or possibly gain privileges via a malformed serializable object.

Weakness: CWE-264

## Which versions are affected by CVE-2016-6526?

It affects 1 product.


Products: Samsung Samsung Mobile.

## How do I fix CVE-2016-6526?

No fix has been published for CVE-2016-6526 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-6526 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-9139](https://insights.sbomify.com/CVE-2018-9139/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-9143](https://insights.sbomify.com/CVE-2018-9143/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-5538](https://insights.sbomify.com/CVE-2017-5538/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9965](https://insights.sbomify.com/CVE-2016-9965/): Denial of service in n/a (critical 9.8)
- [CVE-2016-9966](https://insights.sbomify.com/CVE-2016-9966/): Denial of service in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6526 and fix it if it is affected.

What it is: CVE-2016-6526 is a high-severity unsafe deserialization vulnerability in n/a, published on 18 Jan 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-6526 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-2016-6526/ (Markdown: https://insights.sbomify.com/CVE-2016-6526/index.md)
```

## Sources

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

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