CVE-2023-5632: Unconditionally adding an event to the epoll causes excessive CPU consumption
First published: Wed Oct 18 2023(Updated: )
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 of service type attack. This issue is fixed in 2.0.6
Credit: emo@eclipse.org emo@eclipse.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| <2.0.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID of this issue?
The vulnerability ID of this issue is CVE-2023-5632.
What is the severity rating of CVE-2023-5632?
CVE-2023-5632 has a severity rating of 7.5 (high).
How does this vulnerability affect Eclipse Mosquito?
This vulnerability affects Eclipse Mosquito versions before and including 2.0.5.
What is the impact of this vulnerability?
This vulnerability can be exploited by a malicious actor to perform a denial of service attack by causing excessive CPU consumption in the mosquitto server.
How can I fix this vulnerability?
To fix this vulnerability, update Eclipse Mosquito to version 2.0.6 or later.
- collector/nvd-index
- agent/references
- agent/author
- agent/type
- collector/epss-latest
- source/FIRST
- agent/remedy
- agent/weakness
- agent/epss
- agent/title
- agent/severity
- agent/first-publish-date
- agent/description
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- agent/event
- vendor/eclipse
- canonical/eclipse mosquitto