Security Resilience

CVE-2023-0954

Johnsoncontrols Illustra Pro Gen 4 Dome Firmware ≤ ss016.05.09.04.0006

Published
08 June 2023
Modified
21 November 2024
CVSS Score v3.1 8.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0067 53th percentile
Risk Priority 63 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-0954 is a high-severity Active Debug Code (CWE-489) vulnerability in Johnsoncontrols Illustra Pro Gen 4 Dome Firmware. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A debug feature in Sensormatic Electronics Illustra Pro Gen 4 Dome and PTZ cameras allows a user to compromise credentials after a long period of sustained attack.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1584.004 Server Resource Development
Adversaries may compromise third-party servers that can be used during targeting.
T1584.008 Network Devices Resource Development
Adversaries may compromise third-party network devices that can be used during targeting.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1137.002 Office Test Persistence
Adversaries may abuse the Microsoft Office "Office Test" Registry key to obtain persistence on a compromised system.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-4804Same vendor: Johnsoncontrols
CVE-2026-40035Shared CWE-489
CVE-2026-32662Shared CWE-489
CVE-2026-66403Shared CWE-489
CVE-2024-46873Shared CWE-489
CVE-2026-77545Shared CWE-489
CVE-2025-52663Shared CWE-489
CVE-2026-115727Shared CWE-489
CVE-2024-29075Shared CWE-489
CVE-2026-0169Shared CWE-489

Affected Assets

johnsoncontrols
illustra pro gen 4 dome firmware
≤ ss016.05.09.04.0006
johnsoncontrols
illustra pro gen 4 ptz firmware
≤ ss010.05.09.04.0022

Mitigating Controls

Likely Mitigating Controls

Our mappings. 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.

addresses: CWE-489

Minimal functionality precludes inclusion of active debug code or diagnostic interfaces.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development and acceptance catches active debug code before deployment.

blocks

Configuration management can disable or remove debug features through hardened baselines.

blocks

A.8.20's firewalls, network authentication and segregation can block external network access to debug interfaces, denying the attacker use of the weakness over part of the path, but the debug code remains present and exploitable from within the network or via any interface the controls do not reach.

prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

finds

A.8.30's programme requires the supplier to implement secure development and testing practices (8.25–8.29), acceptance testing, and evidence of testing for malicious content and known vulnerabilities, which would surface active debug code through SAST, code review, and acceptance testing; however, the clause is a contractual/process control whose effect is mediated through supplier compliance and evidence documentation rather than direct testing, so only a minority of instances are reliably found.

blocks

Change management can enforce removal of debug code as part of release gates.

References