# CVE-2022-37025: Privilege escalation in n/a

> A local attacker can modify a configuration file to bypass integrity checks, enabling a LOLBin attack that results in elevated permissions and arbitrary code execution.

- **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:** 18 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-58cr-5qrg-w3pj

## What is CVE-2022-37025?

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

### Official description

An improper privilege management vulnerability in McAfee Security Scan Plus (MSS+) before 4.1.262.1 could allow a local user to modify a configuration file and perform a LOLBin (Living off the land) attack. This could result in the user gaining elevated permissions and being able to execute arbitrary code due to lack of an integrity check of the configuration file.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2022-37025?

It affects 1 product.


Products: Mcafee Security Scan Plus.

## How do I fix CVE-2022-37025?

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

## Is CVE-2022-37025 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8008](https://insights.sbomify.com/CVE-2016-8008/): Privilege escalation in Security Scan Plus (SSP) (high 8.8)
- [CVE-2016-8026](https://insights.sbomify.com/CVE-2016-8026/): Privilege escalation in McAfee Security Scan Plus (SSP) (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37025 and fix it if it is affected.

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

## Sources

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

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