# CVE-2019-14257: Privilege escalation in n/a

> Local attackers can escalate privileges in Zenoss by manipulating environment variables to redirect execution before privileges are dropped.

- **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:** No
- **Published:** 21 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rwrc-9gjv-85pj

## What is CVE-2019-14257?

CVE-2019-14257 is a high-severity vulnerability in n/a, published on 21 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

pyraw in Zenoss 2.5.3 allows local privilege escalation by modifying environment variables to redirect execution before privileges are dropped, aka ZEN-31765.

Weakness: CWE-264

## Which versions are affected by CVE-2019-14257?

It affects 1 product.


Products: Zenoss Zenoss.

## How do I fix CVE-2019-14257?

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

## Is CVE-2019-14257 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14258](https://insights.sbomify.com/CVE-2019-14258/): XML external entity in n/a (high 7.5)
- [CVE-2010-0713](https://insights.sbomify.com/CVE-2010-0713/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2010-0712](https://insights.sbomify.com/CVE-2010-0712/): SQL injection in n/a (medium 6.5)
- [CVE-2014-3739](https://insights.sbomify.com/CVE-2014-3739/): Open redirect in n/a (medium 5.8)
- [CVE-2014-3738](https://insights.sbomify.com/CVE-2014-3738/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14257 and fix it if it is affected.

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

## Sources

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

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