Unauthenticated broker crash via excessive memory allocation
Published Sep 12, 2024 · Updated Oct 30, 2024
Denial of service in Octavo Labs VerneMQ 2.0.1 allows remote attackers to crash the broker through excessive memory consumption. The public record identifies uncontrolled memory allocation but does not disclose the responsible code locus, MQTT operation, or crafted input because its sole proof reference is unavailable. No authentication or user interaction is required, and the reported consequence is loss of broker availability rather than data access or modification.
Summary
What happened
Denial of service in Octavo Labs VerneMQ 2.0.1 allows remote attackers to crash the broker through excessive memory consumption. The public record identifies uncontrolled memory allocation but does not disclose the responsible code locus, MQTT operation, or crafted input because its sole proof reference is unavailable. No authentication or user interaction is required, and the reported consequence is loss of broker availability rather than data access or modification.
The record
- CVE
- CVE-2024-44459
- Published
- Sep 12, 2024
- Updated
- Oct 30, 2024
- Vendor
- Octavo Labs
- Product
- VerneMQ
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 12, 2024CVE publishedPublication date reported by the CVE source.
- Oct 30, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo