Remote code execution via unchecked token entry count
Published Mar 22, 2025 · Updated Nov 3, 2025
Stack-based buffer overflow in Corosync 3.1.9 and earlier allows remote attackers to execute code via a large UDP ORF token. orf_token_endian_convert trusts the packet's rtr_list_entries count and writes converted entries beyond a 1,500-byte token_convert stack buffer. The packet path is reachable when encryption is disabled or the encryption key is known, and exploitation can crash the cluster process or execute code.
Summary
What happened
Stack-based buffer overflow in Corosync 3.1.9 and earlier allows remote attackers to execute code via a large UDP ORF token. orf_token_endian_convert trusts the packet's rtr_list_entries count and writes converted entries beyond a 1,500-byte token_convert stack buffer. The packet path is reachable when encryption is disabled or the encryption key is known, and exploitation can crash the cluster process or execute code.
The record
- CVE
- CVE-2025-30472
- Published
- Mar 22, 2025
- Updated
- Nov 3, 2025
- Vendor
- Corosync
- Product
- Corosync
- Classifications
- CWE-121, CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 22, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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=0 <=3.1.9
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
- UDP ORF-token crash reproducerfunctional · 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