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

> A remote attacker can escalate privileges by manipulating server status codes in Orbe ONetView Reader devices.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2025
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-4xph-hcw4-77x7

## What is CVE-2024-57778?

CVE-2024-57778 is a high-severity vulnerability in n/a, published on 14 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in Orbe ONetView Roeador Onet-1200 Orbe 1680210096 allows a remote attacker to escalate privileges via the servers response from status code 500 to status code 200.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-57778 being exploited?

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

Public exploit code:

- An issue in Orbe ONetView Roteador Onet-1200 Orbe 1680210096 allows a remote attacker to escalate privileges via the servers response from status code 500 to status code 200  (github_poc): https://github.com/KUK3N4N/CVE-2024-57778

## Fix prompt for AI coding agents

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

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

## Sources

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

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