N.V.K.INTER CO., LTD. (NVK) iBSG v3.5 was discovered to contain a hardcoded root password that allows attackers to login with root privileges via the SSH service. The cleartext password corresponding to the $1$4Tmm01jl$7HRvcW.bz7uGmX9hiQWvR hash was not determined by the vulnerability discoverer.
Security readout for executives and security teams
Plain-English summary
NVK iBSG v3.5 reportedly contains a hardcoded root password reachable through SSH. If an attacker can reach SSH and use the credential, they could gain full administrative control of the device. The source bundle does not provide CVSS, a confirmed plaintext password, or a named vendor fix.
Executive priority
Treat this as a high-priority exposure review for any NVK iBSG v3.5 deployment. Business urgency is highest when SSH is Internet-facing or reachable from broad internal networks. Confirm inventory first, then reduce management-plane exposure while seeking vendor remediation.
Technical view
CVE-2023-39808 describes a hardcoded root password in N.V.K.INTER CO., LTD. iBSG v3.5. The record references an md5-crypt-style hash, but states the discoverer did not determine the cleartext password. Exploitability depends on SSH reachability and credential knowledge. No CWE, CPE, CVSS, or official remediation is supplied.
Likely exposure
Exposure is most likely limited to organizations running NVK iBSG v3.5 with SSH enabled, especially if reachable from untrusted networks. The bundle does not identify other affected versions, CPEs, or deployment counts.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. The vulnerability is serious because successful SSH login as root would be full device compromise, but the available evidence does not confirm that the plaintext password is public or known.
Researcher notes
The record is sparse: no CVSS, CWE, CPE, fixed version, or official advisory is included. The core claim is hardcoded root access over SSH, but the discoverer reportedly did not determine the plaintext password. Avoid assuming exploit availability without additional sourced evidence.
Mitigation direction
Check NVK guidance for fixed firmware or replacement options.
Restrict SSH to trusted management networks or VPN access.
Disable SSH where it is not operationally required.
Block direct Internet access to device management services.
Do not rely solely on changing normal user passwords.
Isolate or replace unsupported devices if no fix exists.
Validation and detection
Inventory environments for NVK iBSG v3.5 devices.
Verify whether SSH is enabled on each device.
Confirm SSH is not reachable from the public Internet.
Review logs for root SSH login attempts or successes.
Check vendor channels for firmware or advisory updates.
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.
description · low confidence lookup
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
0CVSS vectors
4Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Aug 21, 2023, 00:00 UTC (UTC+00:00)
ADP timelineCVE
Previously entered references were removed because they are not applicable to this CVE Record.
Jul 8, 2026, 22:21 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Jul 9, 2026, 00:27 UTC (UTC+00:00)
ADP provider summaries
CVECVE Program Container
2026-07-08T22:21:05.413Z: Previously entered references were removed because they are not applicable to this CVE Record.