# CVE-2024-55570: Privilege escalation in n/a

> Authenticated users can escalate privileges to Administrator via a single HTTP PUT request in the web GUI.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 3 Mar 2025
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-rvwg-6c86-cxf4

## What is CVE-2024-55570?

CVE-2024-55570 is a medium-severity vulnerability in n/a, published on 3 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

/api/user/users in the web GUI for the Cubro EXA48200 network packet broker (build 20231025055018) fixed in V5.0R14.5P4-V3.3R1 allows remote authenticated users of the application to increase their privileges by sending a single HTTP PUT request with rolename=Administrator, aka incorrect access control.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2024-55570?


## How do I fix CVE-2024-55570?

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

## Is CVE-2024-55570 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-55570 and fix it if it is affected.

What it is: CVE-2024-55570 is a medium-severity vulnerability in n/a, published on 3 Mar 2025. 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-2024-55570 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-2024-55570/ (Markdown: https://insights.sbomify.com/CVE-2024-55570/index.md)
```

## Sources

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

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