# CVE-2022-23768: Neo Information Sys. NIS-HAP11AC remote access and manipulation vulnerability

> Remote attackers can exploit an exposed telnet port to hijack source code and remotely control the home access point.

- **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:** 19 Sep 2022
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-cvgx-ch95-q7h5

## What is CVE-2022-23768?

CVE-2022-23768 is a high-severity vulnerability in Neo Information Systems Co., Ltd Home AP NIS-HAP11AC, published on 19 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This Vulnerability in NIS-HAP11AC is caused by an exposed external port for the telnet service. Remote attackers use this vulnerability to induce all attacks such as source code hijacking, remote control of the device.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Neoinfosys Nis-Hap11ac Firmware.

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

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

## Is CVE-2022-23768 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23768 is a high-severity vulnerability in Neo Information Systems Co., Ltd Home AP NIS-HAP11AC, published on 19 Sep 2022. 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-2022-23768 in the wild and no public exploit code.

Affected product: Neo Information Systems Co., Ltd Home AP NIS-HAP11AC. 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-23768/ (Markdown: https://insights.sbomify.com/CVE-2022-23768/index.md)
```

## Sources

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

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