# CVE-2014-9135: Security feature bypass in n/a

> Remote attackers can spoof origin websites to bypass whitelist protections in the Huawei P7 PackageInstaller module.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** No
- **Published:** 19 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vv3x-pfj8-4r8v

## What is CVE-2014-9135?

CVE-2014-9135 is a medium-severity vulnerability in n/a, published on 19 Dec 2014. 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

The PackageInstaller module in Huawei P7-L10 smartphones before V100R001C00B136 allows remote attackers to spoof the origin website and bypass the website whitelist protection mechanism via a crafted package.

Weakness: CWE-264

## Which versions are affected by CVE-2014-9135?

It affects 1 product.


Products: Huawei P7-L10 Firmware.

## How do I fix CVE-2014-9135?

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

## Is CVE-2014-9135 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2246](https://insights.sbomify.com/CVE-2015-2246/): Information disclosure in P7-L10 V100R001C00B136 and earlier versions (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9135 and fix it if it is affected.

What it is: CVE-2014-9135 is a medium-severity vulnerability in n/a, published on 19 Dec 2014. 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-2014-9135 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-2014-9135/ (Markdown: https://insights.sbomify.com/CVE-2014-9135/index.md)
```

## Sources

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

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