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

> Low-privileged users can escalate to high-privileged roles due to incorrect access control in Mender server software.

- **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:** 20 Jun 2024
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-h4fx-g364-89c4

## What is CVE-2022-45929?

CVE-2022-45929 is a high-severity vulnerability in n/a, published on 20 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Northern.tech Mender 3.3.x before 3.3.2, 3.5.x before 3.5.0, and 3.6.x before 3.6.0 has Incorrect Access Control and allows users to change their roles and could allow privilege escalation from a low-privileged read-only user to a high-privileged user.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2022-45929 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45929 is a high-severity vulnerability in n/a, published on 20 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45929 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-45929/ (Markdown: https://insights.sbomify.com/CVE-2022-45929/index.md)
```

## Sources

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

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