LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-23768 affects Neo Information Systems Home AP NIS-HAP11AC. The issue is an exposed Telnet service that may let an unauthenticated attacker take control of the device or manipulate it. Treat affected devices as high risk if Telnet is reachable from untrusted networks.

Executive priority

Prioritize this where the affected access point is deployed in business, branch, or remote-office networks. Device takeover risk can undermine network trust and availability, but urgency depends on whether Telnet is reachable from untrusted networks.

Technical view

The CVE describes improper access control, CWE-284, in NIS-HAP11AC version V3.0-B20201117095902. The CVSS 3.1 score is 8.8, with no privileges or user interaction required and high confidentiality, integrity, and availability impact. The CVSS vector lists adjacent-network access, while the description references remote attackers.

Likely exposure

Exposure is likely limited to Home AP NIS-HAP11AC devices running V3.0-B20201117095902 with Telnet exposed beyond trusted administration networks. The bundle provides no CPEs and names only one affected version.

Exploitation context

The provided data does not show CISA KEV listing or confirmed active exploitation. Public descriptions state attackers may remotely control or manipulate the device through the exposed Telnet service, but no exploit availability or campaign evidence is provided.

Researcher notes

Evidence is sparse and centered on the CVE record and KRCERT reference. Key uncertainties are vendor remediation status, whether other firmware builds are affected, and whether the exposed Telnet service is reachable beyond adjacent networks in real deployments.

Mitigation direction

  • Identify any Home AP NIS-HAP11AC devices and firmware versions in use.
  • Check Neo Information Systems or KRCERT guidance for supported firmware or configuration fixes.
  • Remove Telnet exposure from untrusted networks while confirming vendor guidance.
  • Restrict device administration to trusted management networks only.
  • Replace unsupported affected devices if no vendor-supported remediation is available.

Validation and detection

  • Inventory devices for model Home AP NIS-HAP11AC and version V3.0-B20201117095902.
  • Verify whether Telnet is reachable from guest, user, external, or unmanaged networks.
  • Review router administration settings against vendor or KRCERT remediation guidance.
  • Confirm monitoring covers unexpected administrative access or configuration changes on affected devices.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-23768 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-23768Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Neo Information Systems Co., LtdHome AP NIS-HAP11ACV3.0-B20201117095902Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.