Broker crash via freed socket pointer dereference
Published Feb 26, 2024 · Updated Oct 27, 2024
Use-after-free in NanoMQ 0.21.2 allows remote authenticated users to crash the broker through network-accessible socket handling. In socket.c, sock_destroy passes pointer s to nni_free, but later code dereferences s->s_id after the allocation has been released. Low-privileged network access is required, and the reported consequence is service interruption rather than data disclosure or modification.
Summary
What happened
Use-after-free in NanoMQ 0.21.2 allows remote authenticated users to crash the broker through network-accessible socket handling. In socket.c, sock_destroy passes pointer s to nni_free, but later code dereferences s->s_id after the allocation has been released. Low-privileged network access is required, and the reported consequence is service interruption rather than data disclosure or modification.
The record
- CVE
- CVE-2024-25767
- Published
- Feb 26, 2024
- Updated
- Oct 27, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2024CVE publishedPublication date reported by the CVE source.
- Oct 27, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
- NanoMQ socket.c use-after-free demonstrationproof of concept · demonstrated
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