Corosync up to 3.1.9 exec/totemsrp.c orf_token_endian_convert stack-based overflow

Summaryinfo

A vulnerability, which was classified as critical, has been found in Corosync up to 3.1.9. The impacted element is the function orf_token_endian_convert of the file exec/totemsrp.c. This manipulation causes stack-based overflow. This vulnerability is tracked as CVE-2025-30472. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability classified as critical was found in Corosync up to 3.1.9. Affected by this vulnerability is the function orf_token_endian_convert of the file exec/totemsrp.c. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Corosync through 3.1.9, if encryption is disabled or the attacker knows the encryption key, has a stack-based buffer overflow in orf_token_endian_convert in exec/totemsrp.c via a large UDP packet.

The advisory is shared at github.com. This vulnerability is known as CVE-2025-30472 since 03/22/2025. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/07/2025).

The vulnerability scanner Nessus provides a plugin with the ID 233752 (SUSE SLES15 / openSUSE 15 Security Update : corosync (SUSE-SU-2025:1084-1)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (233752) and EUVD (EUVD-2025-7198). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Corosync

Version

• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3
• 3.1.4
• 3.1.5
• 3.1.6
• 3.1.7
• 3.1.8
• 3.1.9

Website

• Product: https://github.com/corosync/corosync/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion