# CVE-2022-3203: ORing net IAP-420(+) Hidden Functionality

> Attackers can gain administrative shell access via hardcoded credentials on ORing IAP-420 devices, as the telnet server is enabled by default and cannot be permanently disabled.

- **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:** 21 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-4hvx-h8mx-pjgh

## What is CVE-2022-3203?

CVE-2022-3203 is a critical vulnerability in ORing IAP-420(+), published on 21 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On ORing net IAP-420(+) with FW version 2.0m a telnet server is enabled by default and cannot permanently be disabled. You can connect to the device via LAN or WiFi with hardcoded credentials and get an administrative shell. These credentials are reset to defaults with every reboot.

Weakness: CWE-912 (Hidden Functionality)

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

It affects 2 products.


Products: Oringnet Iap-420\+ Firmware, Oringnet Iap-420 Firmware.

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

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

## Is CVE-2022-3203 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3203 is a critical vulnerability in ORing IAP-420(+), published on 21 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3203 exists.

Affected product: ORing IAP-420(+). 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-3203/ (Markdown: https://insights.sbomify.com/CVE-2022-3203/index.md)
```

## Sources

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

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