Security Resilience

CVE-2023-5632

DoS in Eclipse Mosquitto 2.0.5

Published
18 October 2023
Modified
25 June 2025
Patch / 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.0069 52th 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-5632 is a high-severity Excessive Iteration (CWE-834) vulnerability in Eclipse Mosquitto. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

In Eclipse Mosquito before and including 2.0.5, establishing a connection to the mosquitto server without sending data causes the EPOLLOUT event to be added, which results excessive CPU consumption. This could be used by a malicious actor to perform denial…

more

of service type attack. This issue is fixed in 2.0.6

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-8376Same product: Eclipse Mosquitto
CVE-2023-28366Same product: Eclipse Mosquitto
CVE-2024-3935Same product: Eclipse Mosquitto
CVE-2023-0809Same product: Eclipse Mosquitto
CVE-2024-10525Same product: Eclipse Mosquitto
CVE-2023-3592Same product: Eclipse Mosquitto
CVE-2023-4043Same vendor: Eclipse
CVE-2026-16439Same vendor: Eclipse
CVE-2026-58080Same vendor: Eclipse
CVE-2026-10051Same vendor: Eclipse

Affected Assets

eclipse
mosquitto
2.0.5

Mitigating Controls

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 requires input validation and loop bounds, directly limiting excessive iteration.

blocks

Application security requirements include resource-consumption limits that prevent unbounded loops.

blocks

Secure architecture principles mandate defensive coding patterns such as loop termination checks.

prevents

Secure coding standards explicitly forbid unbounded loops and require explicit iteration limits.

finds

Security testing can detect excessive iteration through stress and fuzz testing.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-834, a class-level weakness, and none of its children carries one either.

References