Security Resilience

CVE-2023-5393

Published
11 April 2024
Modified
15 April 2026
CVSS Score v3.1 7.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS Score 0.0071 53th percentile
Risk Priority 58 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-5393 is a high-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Honeywell Security Notification (inferred from references). Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Server receiving a malformed message that causes a disconnect to a hostname may causing a stack overflow resulting in possible remote code execution. Honeywell recommends updating to the most recent version of the product. See Honeywell Security Notification for recommendations…

more

on upgrading and versioning.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-5706Shared CWE-130
CVE-2026-110912Shared CWE-130
CVE-2024-38011Shared CWE-130
CVE-2026-90678Shared CWE-130
CVE-2026-5265Shared CWE-130
CVE-2023-53157Shared CWE-130
CVE-2025-14847Shared CWE-130
CVE-2024-42460Shared CWE-130
CVE-2024-37989Shared CWE-130
CVE-2026-101942Shared CWE-130

Affected Assets

Honeywell
Security Notification
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.5
  • V4.2.1
  • V4.2.2

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover length-parameter inconsistencies through targeted parsing tests.

Input validation enforces correct length-to-data consistency checks on parsed messages before processing.

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.

PR.PS-06 partial match
blocks

Secure SDLC practices directly enforce length validation and input sanitization during coding and review.

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.

blocks

Secure development lifecycle mandates input validation and length checks that directly address inconsistent length fields.

blocks

Application security requirements include explicit rules for handling message lengths and data structures.

blocks

A.8.27 mandates security-by-design, defence-in-depth, distrust-external-input, secure session control, data validation/sanitisation and design reviews against known attack patterns; these reach a minority slice of length-parameter inconsistencies (especially where they surface as input-handling or parsing flaws) but leave the bulk of protocol/message-parsing bugs untouched.

prevents

Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.

finds

Security testing in development can detect length-inconsistency vulnerabilities before deployment.

References