# CVE-2014-3222: Privilege escalation in eSpace Meeting V100R001C03SPC201 and the earlier versions

> Attackers with common user permissions can elevate privileges to access and modify key resources in Huawei eSpace Meeting.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p237-6fqh-2765

## What is CVE-2014-3222?

CVE-2014-3222 is a high-severity vulnerability in eSpace Meeting V100R001C03SPC201 and the earlier versions, published on 2 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Huawei eSpace Meeting with software V100R001C03SPC201 and the earlier versions, attackers that obtain the permissions assigned to common users can elevate privileges to access and set specific key resources.

Weakness: CWE-264

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

It affects 1 product.


Products: Huawei Espace Meeting.

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

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

## Is CVE-2014-3222 being exploited?

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

Public exploit code:

- Huawei Technologies eSpace Meeting Service 1.0.0.23 - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3222 is a high-severity vulnerability in eSpace Meeting V100R001C03SPC201 and the earlier versions, published on 2 Apr 2017. 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-2014-3222 in the wild and no public exploit code.

Affected product: eSpace Meeting V100R001C03SPC201 and the 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-2014-3222/ (Markdown: https://insights.sbomify.com/CVE-2014-3222/index.md)
```

## Sources

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

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