# CVE-2014-1845: Privilege escalation in n/a

> Local attackers can gain root privileges via a setuid helper in Enlightenment that fails to sanitize the environment.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/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:** Yes
- **Published:** 27 Apr 2018
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-1845, GHSA-w3w7-92w5-6f8r

## What is CVE-2014-1845?

CVE-2014-1845 is a high-severity vulnerability in n/a, published on 27 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An unspecified setuid root helper in Enlightenment before 0.17.6 allows local users to gain privileges by leveraging failure to properly sanitize the environment.

Weakness: CWE-264

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

It affects 1 product.


Products: Enlightenment Enlightenment.

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

Upgrade to a fixed version.

## Is CVE-2014-1845 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-37706](https://insights.sbomify.com/CVE-2022-37706/): Privilege escalation in n/a (high 7.8)
- [CVE-2014-1846](https://insights.sbomify.com/CVE-2014-1846/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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