# CVE-2016-6587: Information disclosure in Norton Mobile Security for Android

> A local attacker can read sensitive information from the mid.dat file on the SD card in Norton Mobile Security for Android.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9hjc-v342-97r7

## What is CVE-2016-6587?

CVE-2016-6587 is a medium-severity vulnerability in Symantec Norton Mobile Security for Android, published on 8 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Information Disclosure vulnerability exists in the mid.dat file stored on the SD card in Symantec Norton Mobile Security for Android before 3.16, which could let a local malicious user obtain sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Symantec Norton Mobile Security.

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

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

## Is CVE-2016-6587 being exploited?

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

## Other vulnerabilities in Symantec Norton Mobile Security for Android

- [CVE-2016-6585](https://insights.sbomify.com/CVE-2016-6585/): Denial of service in Norton Mobile Security for Android (medium 5.3)
- [CVE-2016-6586](https://insights.sbomify.com/CVE-2016-6586/): Security feature bypass in Norton Mobile Security for Android (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6587 is a medium-severity vulnerability in Symantec Norton Mobile Security for Android, published on 8 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6587 in the wild and no public exploit code.

Affected product: Symantec Norton Mobile Security for Android. 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-6587/ (Markdown: https://insights.sbomify.com/CVE-2016-6587/index.md)
```

## Sources

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

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