# CVE-2021-28250: Privilege escalation in n/a

> Local attackers can escalate privileges to the ehealth user by exploiting a setuid executable in the unsupported CA eHealth Performance Manager.

- **Severity:** High 7.8 (`CVSS:3.1/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:** 26 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jh68-p5rf-gmh3

## What is CVE-2021-28250?

CVE-2021-28250 is a high-severity vulnerability in n/a, published on 26 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CA eHealth Performance Manager through 6.3.2.12 is affected by Privilege Escalation via a setuid (and/or setgid) file. When a component is run as an argument of the runpicEhealth executable, the script code will be executed as the ehealth user. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2021-28250?

It affects 1 product.


Products: Ca Ehealth Performance Manager.

## How do I fix CVE-2021-28250?

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

## Is CVE-2021-28250 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-28249](https://insights.sbomify.com/CVE-2021-28249/): Privilege escalation in n/a (high 8.8)
- [CVE-2021-28247](https://insights.sbomify.com/CVE-2021-28247/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2010-0640](https://insights.sbomify.com/CVE-2010-0640/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28250 and fix it if it is affected.

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

## Sources

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

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