Cyber Resilience

CVE-2023-28366

Eclipse Mosquitto 1.3.2 – 2.0.16

Published
01 September 2023
Modified
26 June 2025
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.011 63th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2023-28366 is a high-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Eclipse Mosquitto. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

The broker in Eclipse Mosquitto 1.3.2 through 2.x before 2.0.16 has a memory leak that can be abused remotely when a client sends many QoS 2 messages with duplicate message IDs, and fails to respond to PUBREC commands. This occurs…

more

because of mishandling of EAGAIN from the libc send function.

CWE(s)
CWE-401

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-3592Same product: Eclipse Mosquitto
CVE-2023-5632Same product: Eclipse Mosquitto
CVE-2024-8376Same product: Eclipse Mosquitto
CVE-2023-0809Same product: Eclipse Mosquitto
CVE-2024-3935Same product: Eclipse Mosquitto
CVE-2026-63252Same vendor: Eclipse
CVE-2024-10525Same product: Eclipse Mosquitto
CVE-2024-7708Same vendor: Eclipse
CVE-2026-1605Same vendor: Eclipse
CVE-2026-46102Shared CWE-401

Affected Assets

eclipse
mosquitto
1.3.2 — 2.0.16

Mitigating Controls

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 mostly match
prevents

Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.

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.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect unreleased memory, providing partial coverage of the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates memory-management practices that reduce missing-release defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify explicit memory-release rules, partially mitigating the weakness.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles include resource-management guidelines that address memory leaks.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.

A.8.6 Capacity management partial match
finds

Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.

References