CVE-2023-40158
Cbc Nr4H Firmware
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-40158 is a high-severity Hidden Functionality (CWE-912) vulnerability in Cbc Nr4H Firmware. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Redundant Access (T1108); ranked in the top 32% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-40158 is a hidden functionality vulnerability affecting certain CBC products from Ganz Security, including the NR4H, NR8H, NR16H, DR-16F, DR-8F, DR-4F, DR-16H, DR-8H, DR-4H, and DR-4M41 series. The flaw permits a remote authenticated attacker to execute arbitrary operating system commands on the device or modify its configuration settings. Several of the listed product lines are end-of-life and receive no vendor updates.
An attacker with valid low-privileged credentials can exploit the issue over the network without user interaction. Successful exploitation yields full control over the affected device, enabling arbitrary command execution and configuration changes that impact confidentiality, integrity, and availability.
Vendor advisories published on ganzsecurity.com and coordinated through JVN recommend applying the security notices referenced in the product release pages. Unsupported models receive no patches, leaving them permanently exposed.
The associated EPSS score has remained flat at 0.0612 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-44765
Vulnerability Data
Hidden functionality vulnerability in the CBC products allows a remote authenticated attacker to execute an arbitrary OS command on the device or alter its settings. As for the affected products/versions, see the detailed information provided by the vendor. Note that…
more
NR4H, NR8H, NR16H series and DR-16F, DR-8F, DR-4F, DR-16H, DR-8H, DR-4H, DR-4M41 series are no longer supported, therefore updates for those products are not provided.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Documenting every system component at the required granularity and reviewing the inventory detects or prevents hidden functionality from remaining undetected.
Recovery eliminates hidden functionality or backdoors introduced during compromise.
Policy requires supplier transparency and testing to detect hidden functionality or backdoors inserted in the supply chain.
Screening high-risk technical positions lowers the probability that hidden functionality or backdoors will be added by authorized personnel.
Hunting identifies hidden functionality used for persistence or evasion after initial compromise.
TSCM surveys discover and eliminate hidden surveillance functionality that would otherwise remain undetected in the environment.
Change control, approval gates, and flaw tracking force hidden functionality to be either documented or discovered and removed.
Vetting and integrity controls during acquisition reduce the likelihood of hidden backdoors or malicious functionality introduced by suppliers.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can discover undocumented functionality before release.
Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.
Secure development life cycle mandates documented requirements and design reviews that would expose undocumented hidden functionality.
Application security requirements explicitly define expected functionality, making hidden features a violation.
Secure system architecture and engineering principles require transparent, documented designs that preclude hidden functionality.