REDHAT-BUG-2453813: Medium severity corosync corosync vulnerability
Wrong return value vulnerability in the Corosync membership commit token sanity check in exec/totemsrp.c. The flaw occurs in checkmembcommittokensanity() where truncated messages (msglen < sizeof(struct membcommittoken)) incorrectly return 0 (success) instead of -1 (failure). As a result, messagehandlermembcommittoken() continues processing attacker-controlled, undersized input, performs an allocation based on the short length, and then accesses struct membcommittoken fields beyond the allocated region, triggering an out-of-bounds read (ASAN-confirmed). This can be exploited remotely without authentication in totemudp/totemudpu mode by sending a single crafted UDP packet to the Corosync port (default 5405), causing a denial of service and potentially leaking limited memory contents.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2453813?
The severity of REDHAT-BUG-2453813 has not been explicitly rated, but it involves a wrong return value that could potentially lead to security issues.
How do I fix REDHAT-BUG-2453813?
To fix REDHAT-BUG-2453813, you should apply the latest patches or updates provided by Corosync for the affected versions.
What could happen if REDHAT-BUG-2453813 is exploited?
If REDHAT-BUG-2453813 is exploited, it may allow truncated messages to be incorrectly processed, potentially impacting the stability of the Corosync service.
What versions of Corosync are affected by REDHAT-BUG-2453813?
All versions of Corosync that include the vulnerable code in exec/totemsrp.c are affected by REDHAT-BUG-2453813.
Is there a workaround for REDHAT-BUG-2453813 if I cannot apply a patch immediately?
Currently, there are no documented workarounds for REDHAT-BUG-2453813, so applying a patch is the recommended action.