Corosync: corosync: heap-based buffer overflow in totempg assembly buffer during fragmented message reassembly
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A heap-based buffer overflow was found in Corosync's Totem Process Group (totempg) message reassembly. When processing fragmented multicast messages, the buffer used to reassemble fragments lacks a runtime bounds check in release builds. A network-adjacent attacker able to send crafted multicast protocol messages to the cluster could cause a heap buffer overflow with attacker-controlled data. This can crash the Corosync daemon, causing a denial of service to the entire cluster, and may potentially allow further exploitation given sufficient heap-corruption control.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- corosync
Version range not reported
- openshift/ose-rhel-coreos-9
Version range not reported
- rhcos
Version range not reported