# CVE-2024-53938: Auth bypass in n/a

> Attackers can gain full remote control of the router via Telnet because the root account has no password and the service is enabled by default.

- **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:** 2 Dec 2024
- **Updated:** 3 Dec 2024
- **Also known as:** GHSA-99rp-8r7p-prmv

## What is CVE-2024-53938?

CVE-2024-53938 is a high-severity authentication bypass vulnerability in n/a, published on 2 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Victure RX1800 WiFi 6 Router (software EN_V1.0.0_r12_110933, hardware 1.0) devices. The TELNET service is enabled by default and exposed over the LAN. The root account is accessible without a password, allowing attackers to achieve full control over the router remotely without any authentication.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-53938 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53938 is a high-severity authentication bypass vulnerability in n/a, published on 2 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53938 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-2024-53938/ (Markdown: https://insights.sbomify.com/CVE-2024-53938/index.md)
```

## Sources

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

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