# CVE-2018-14327: Privilege escalation in n/a

> Local attackers can escalate privileges by replacing executables in directories with weak permissions on Alcatel OSPREY3_MINI modems.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 26 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gffw-36xc-qj42

## What is CVE-2018-14327?

CVE-2018-14327 is a high-severity vulnerability in n/a, published on 26 Sep 2018. 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 installer for the Alcatel OSPREY3_MINI Modem component on EE EE40VB 4G mobile broadband modems with firmware before EE40_00_02.00_45 sets weak permissions (Everyone:Full Control) for the "Web Connecton\EE40" and "Web Connecton\EE40\BackgroundService" directories, which allows local users to gain privileges, as demonstrated by inserting a Trojan horse ServiceManager.exe file into the "Web Connecton\EE40\BackgroundService" directory.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-14327?

It affects 1 product.


Products: Ee Ee40vb Firmware.

## How do I fix CVE-2018-14327?

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

## Is CVE-2018-14327 being exploited?

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

Public exploit code:

- EE 4GEE Mini EE40_00_02.00_44 - Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14327 and fix it if it is affected.

What it is: CVE-2018-14327 is a high-severity vulnerability in n/a, published on 26 Sep 2018. 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-2018-14327 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-2018-14327/ (Markdown: https://insights.sbomify.com/CVE-2018-14327/index.md)
```

## Sources

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

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