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

> Man-in-the-middle attackers can downgrade HTTPS to HTTP to execute arbitrary Java code in Kingsoft Office on Huawei devices.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-prx2-gh7q-w297

## What is CVE-2014-2271?

CVE-2014-2271 is a high-severity vulnerability in n/a, published on 14 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

cn.wps.moffice.common.beans.print.CloudPrintWebView in Kingsoft Office 5.3.1, as used in Huawei P2 devices before V100R001C00B043, falls back to HTTP when the HTTPS connection to the registry fails, which allows man-in-the-middle attackers to conduct downgrade attacks and execute arbitrary Java code by leveraging a network position between the client and the registry to block HTTPS traffic.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Huawei P2-6011 Firmware, Wps Wps Office.

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

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

## Is CVE-2014-2271 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2273](https://insights.sbomify.com/CVE-2014-2273/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2271 is a high-severity vulnerability in n/a, published on 14 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2271 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-2271/ (Markdown: https://insights.sbomify.com/CVE-2014-2271/index.md)
```

## Sources

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

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