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

> Attackers can escalate privileges in Another Eden via crafted payloads in vulnerable system driver components.

- **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:** 6 Feb 2023
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-r3fh-95rm-cx6p

## What is CVE-2022-48019?

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

### Official description

The components wfshbr64.sys and wfshbr32.sys in Another Eden before v3.0.20 and before v2.14.200 allows attackers to perform privilege escalation via a crafted payload.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Wfs Another Eden.

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

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

## Is CVE-2022-48019 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48019 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48019 is a high-severity vulnerability in n/a, published on 6 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48019 exists.

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-48019/ (Markdown: https://insights.sbomify.com/CVE-2022-48019/index.md)
```

## Sources

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

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