CVE-2023-41967
Gallagher Controller 6000 Firmware ≤ 8.60
Raw vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-41967 is a low-severity Sensitive Information Uncleared Before Debug/Power State Transition (CWE-1272) vulnerability in Gallagher Controller 6000 Firmware. Its CVSS base score is 2.4 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-46426
Vulnerability Data
Sensitive information uncleared after debug/power state transition in the Controller 6000 could be abused by an attacker with knowledge of the Controller's default diagnostic password and physical access to the Controller to view its configuration through the diagnostic web pages.…
more
This issue affects: Gallagher Controller 6000 8.70 prior to vCR8.70.231204a (distributed in 8.70.2375 (MR5)), v8.60 or earlier.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 3 OS baselines
V14.2.4V14.2.8V14.3.3
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.
Eradication of spilled information from contaminated systems mitigates the effects of improper removal of sensitive data before storage or transfer.
The control requires verified removal of sensitive data before media is made available at a reduced classification level, directly addressing improper removal prior to storage or transfer.
Explicit procedures to delete inaccurate or outdated PII directly mitigate improper removal of sensitive information before storage or transfer.
Retention policies enforce removal or sanitization of sensitive data before storage or transfer per regulatory requirements.
The explicit requirement to delete inaccurate/outdated PII implements proper removal of sensitive information before further storage or transfer.
The control implements proper removal of sensitive information before storage or transfer of datasets.
The generate-on-demand-and-delete requirement enforces removal of sensitive information before storage or transfer, preventing improper retention.
Requires explicit removal of sensitive information prior to component transfer or disposal, reducing exposure from retained data.
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.
Explicitly requires removing confidential data from memory/processes when no longer needed, directly preventing exposure on state transitions.
Integrating secure development practices throughout the SDLC prevents introduction of uncleared-data flaws during design and coding.
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.
A.5.12 only defines and communicates a classification scheme so that protection needs can be understood; per the owner's explicit rule on labelling/classification controls, it has no direct preventing effect on a weakness unless and until another control (access, DLP, etc.) is configured to act on the resulting label.
Information-transfer rules can require sanitization of sensitive content before sharing.
A.5.34 only requires a privacy policy, procedures, assigned roles (e.g. privacy officer) and unspecified technical/organizational measures; it does not itself stop the improper retention of sensitive data before storage/transfer, so the weakness remains exploitable without depending on other controls.
A.8.10 requires deleting or securely erasing sensitive information that is no longer required per retention policy; CWE-1272 is a hardware-level failure to clear data on a debug/power state transition that changes access restrictions, which is neither a retention-driven deletion nor covered by the control's methods or scope.
A.8.11's masking/pseudonymization/anonymization techniques (plus access design and obfuscation rules) stop most exposures of the sensitive data that CWE-212 would otherwise transfer or store in the clear; the bounded remainder is data that must stay unmasked for functional reasons or where masking is not applied to every indirect identifier.
DLP policies can block or sanitize sensitive data before it leaves the system.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248579 OL 8 must restrict access to the kernel message buffer. blocks CWE-212
- V-248580 OL 8 must prevent kernel profiling by unprivileged users. blocks CWE-212
- V-248551 A sticky bit must be set on all OL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. blocks CWE-212
Oracle Linux 9 (1 rule)
- V-271745 OL 9 must restrict access to the kernel message buffer. blocks CWE-212
RHEL 8 (1 rule)
- V-230269 RHEL 8 must restrict access to the kernel message buffer. blocks CWE-212