# CVE-2015-2246: Information disclosure in P7-L10 V100R001C00B136 and earlier versions

> The MeWidget module on Huawei P7 smartphones allows attackers to disclose contact information.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **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:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vp9p-frm6-465h

## What is CVE-2015-2246?

CVE-2015-2246 is a low-severity vulnerability in P7-L10 V100R001C00B136 and earlier versions, published on 2 Apr 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 MeWidget module on Huawei P7 smartphones with software P7-L10 V100R001C00B136 and earlier versions could lead to the disclosure of contact information.

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

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

It affects 1 product.


Products: Huawei P7-L10 Firmware.

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

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

## Is CVE-2015-2246 being exploited?

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

## Other vulnerabilities in P7-L10 V100R001C00B136 and earlier versions

- [CVE-2014-9135](https://insights.sbomify.com/CVE-2014-9135/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2246 is a low-severity vulnerability in P7-L10 V100R001C00B136 and earlier versions, published on 2 Apr 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-2015-2246 in the wild and no public exploit code.

Affected product: P7-L10 V100R001C00B136 and earlier versions. 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-2246/ (Markdown: https://insights.sbomify.com/CVE-2015-2246/index.md)
```

## Sources

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

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