# CVE-2022-46080: Auth bypass in n/a

> Attackers can bypass authentication on Nexxt Nebula routers to enable Telnet and execute arbitrary commands.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2023
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-f9fp-mv38-gcjq

## What is CVE-2022-46080?

CVE-2022-46080 is a critical authentication bypass vulnerability in n/a, published on 6 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nexxt Nebula 1200-AC 15.03.06.60 allows authentication bypass and command execution by using the HTTPD service to enable TELNET.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Nexxtsolutions Nebula1200-Ac Firmware.

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

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

## Is CVE-2022-46080 being exploited?

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

Public exploit code:

- it is script that enables Telnet on routers by sending a specially crafted request. The script allows users to specify the router's URL, Telnet port, and password. It validates the inputs and logs the process, providing feedback on whether the exploit was successful. (github_poc): https://github.com/geniuszly/CVE-2022-46080
- Nexxt Router 15.03.06.60 Authentication Bypass and Remote Command Execution (github_poc): https://github.com/yerodin/CVE-2022-46080

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46080 is a critical authentication bypass vulnerability in n/a, published on 6 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46080 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-46080/ (Markdown: https://insights.sbomify.com/CVE-2022-46080/index.md)
```

## Sources

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

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