CVE-2023-5398
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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-5398 is a medium-severity Binding to an Unrestricted IP Address (CWE-1327) vulnerability in Honeywell Security Notification (inferred from references). Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-57713
Vulnerability Data
Server receiving a malformed message based on a list of IPs resulting in heap corruption causing a denial of service. See Honeywell Security Notification for recommendations on upgrading and versioning.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Establishes the most restrictive configuration settings, which would require binding only to specific addresses rather than 0.0.0.0.
Enforces approved information flow policies that would disallow unrestricted remote bindings.
Enforces least functionality by prohibiting unnecessary network exposure such as unrestricted listening addresses.
Requires control of communications at external and key internal interfaces, preventing binding that accepts traffic from any source.
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.
Documenting authorized network flows informs correct bind decisions and reduces the chance of 0.0.0.0 usage.
Network protection controls directly prevent exposure via unrestricted binds while fixing the weakness addresses only one vector of unauthorized access.
Configuration management enforces restricted bind addresses, covering the weakness completely but only one aspect of overall hardening.
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.
Network security controls directly require restricting listening interfaces to specific addresses rather than 0.0.0.0.
A.8.21 requires identifying, requiring and monitoring security features (including authentication, authorization and network connection controls) from providers and formulating rules on allowed networks/services; it does not stop a product from binding to 0.0.0.0 and the weakness remains exploitable until the binding itself is changed.
Network segregation can limit the blast radius of an unrestricted binding but does not prevent the binding itself.
Secure architecture principles discourage exposing services on all interfaces, though the control is broader than this single weakness.
Secure coding guidance can catch hard-coded 0.0.0.0 bindings during development but is not the primary mitigation.