CVE-2013-0250

NONECVSS 0.0

0.0

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.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 76.7%
KEV: Not listed

Published

June 6, 2014

Last Modified

May 6, 2026

References (10)

secalert@redhathttp://seclists.org/oss-sec/2013/q1/212
secalert@redhathttp://seclists.org/oss-sec/2013/q1/213
secalert@redhathttp://seclists.org/oss-sec/2013/q1/214
secalert@redhathttp://secunia.com/advisories/52037
secalert@redhathttps://github.com/corosync/corosync/commit/b3f456a8ceefac6e9f2e9acc2ea0c159d412b595
af854a3a-2127-422b-91ae-364da2661108http://seclists.org/oss-sec/2013/q1/212
af854a3a-2127-422b-91ae-364da2661108http://seclists.org/oss-sec/2013/q1/213
af854a3a-2127-422b-91ae-364da2661108http://seclists.org/oss-sec/2013/q1/214
af854a3a-2127-422b-91ae-364da2661108http://secunia.com/advisories/52037
af854a3a-2127-422b-91ae-364da2661108https://github.com/corosync/corosync/commit/b3f456a8ceefac6e9f2e9acc2ea0c159d412b595

Data Freshness Timeline

(refreshed 8× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

2026-06-08 14:14 UTCEPSS rescore
2026-06-07 15:22 UTCEPSS rescore
2026-06-06 13:45 UTCEPSS rescore
2026-06-06 13:45 UTCEPSS rescore
2026-06-05 22:44 UTCEPSS rescore
2026-06-05 22:44 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-02 20:10 UTCEPSS rescore
2026-06-02 20:10 UTCEPSS rescore
2026-06-01 13:49 UTCEPSS rescore
2026-06-01 13:49 UTCEPSS rescore
2026-05-31 22:28 UTCEPSS rescore
2026-05-31 22:28 UTCEPSS rescore
2026-05-31 00:14 UTCEPSS rescore
2026-05-31 00:14 UTCEPSS rescore
2026-05-29 13:41 UTCEPSS rescore
2026-05-29 13:41 UTCEPSS rescore
2026-05-28 18:36 UTCEG score recompute
2026-05-28 18:36 UTCGHSA enrichment

Frequently asked(4)

What is CVE-2013-0250?

CVE-2013-0250 is a none vulnerability published on June 6, 2014. The initnsshash 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.

When was CVE-2013-0250 disclosed?

CVE-2013-0250 was first published in the National Vulnerability Database on June 6, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2013-0250 actively exploited?

CVE-2013-0250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 76.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2013-0250?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-0250, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-0250

Explore →

Is Your Infrastructure Affected by CVE-2013-0250?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2013-0250

📅 Published

🔄 Last Modified

🔗 References (10)