CVE-2013-0250
CVE-2013-0250 is a medium-severity vulnerability in Corosync with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- Severity: Medium (CVSS 2.0 base score 5.0)
- EPSS exploit prediction: 3% (86th percentile)
- Actively exploited: Not listed in CISA KEV
- Affected product: Corosync
- Published:
- Last modified:
Description
The init_nss_hash function in exec/totemcrypto.c in Corosync 2.0 before 2.3 does not properly initialize the HMAC key, which allows remote attackers to cause a denial of service (crash) via a crafted packet.
Frequently asked questions
- What is CVE-2013-0250?
- The init_nss_hash function in exec/totemcrypto.c in Corosync 2.0 before 2.3 does not properly initialize the HMAC key, which allows remote attackers to cause a denial of service (crash) via a crafted packet.
- How severe is CVE-2013-0250?
- CVE-2013-0250 has a CVSS 2.0 base score of 5.0, rated medium severity.
- Is CVE-2013-0250 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (86th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2013-0250?
- CVE-2013-0250 primarily affects Corosync. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2013-0250?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2013-0250 published?
- CVE-2013-0250 was published on 2014-06-06 and last updated on 2026-06-16.
References
- http://seclists.org/oss-sec/2013/q1/212
- http://seclists.org/oss-sec/2013/q1/213
- http://seclists.org/oss-sec/2013/q1/214
- http://secunia.com/advisories/52037
- https://github.com/corosync/corosync/commit/b3f456a8ceefac6e9f2e9acc2ea0c159d412b595
Affected products (7)
- cpe:2.3:a:corosync:corosync:2.0.0:*:*:*:*:*:*:*
- cpe:2.3:a:corosync:corosync:2.0.1:*:*:*:*:*:*:*
- cpe:2.3:a:corosync:corosync:2.0.2:*:*:*:*:*:*:*
- cpe:2.3:a:corosync:corosync:2.0.3:*:*:*:*:*:*:*
- cpe:2.3:a:corosync:corosync:2.1.0:*:*:*:*:*:*:*
- cpe:2.3:a:corosync:corosync:2.1.1:*:*:*:*:*:*:*
- cpe:2.3:a:corosync:corosync:2.2.0:*:*:*:*:*:*:*
More vulnerabilities in Corosync
- CVE-2025-30472 — Critical (CVSS 9.0): Corosync through 3.1.9, if encryption is disabled or the attacker knows the encryption key, has a stack-based buffer…
- CVE-2026-35091 — High (CVSS 8.2): A flaw was found in Corosync. A remote unauthenticated attacker can exploit a wrong return value vulnerability in the…
- CVE-2026-35092 — High (CVSS 7.5): A flaw was found in Corosync. An integer overflow vulnerability in Corosync's join message sanity validation allows a…
- CVE-2018-1084 — High (CVSS 7.5): corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c.