# CVE-2022-47531: Security feature bypass in n/a

> Authenticated users can bypass the system CLI to execute commands directly in the UNIX shell, leading to privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-h8q3-6873-qc83

## What is CVE-2022-47531?

CVE-2022-47531 is a high-severity vulnerability in n/a, published on 5 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Ericsson Evolved Packet Gateway (EPG) versions 3.x before 3.25 and 2.x before 2.16, allows authenticated users to bypass system CLI and execute commands they are authorized to execute directly in the UNIX shell.

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

It affects 1 product.


Products: Ericsson Evolved Packet Gateway.

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

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

## Is CVE-2022-47531 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47531 is a high-severity vulnerability in n/a, published on 5 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-47531 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-47531/ (Markdown: https://insights.sbomify.com/CVE-2022-47531/index.md)
```

## Sources

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

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