| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Corosync up to 2.2.0. It has been classified as problematic. This vulnerability affects the function init_nss_hash. Performing a manipulation results in initialization.
This vulnerability was named CVE-2013-0250. There is no available exploit.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Corosync up to 2.2.0. It has been classified as problematic. This affects the function init_nss_hash. The manipulation with an unknown input leads to a initialization vulnerability. CWE is classifying the issue as CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. This is going to have an impact on availability. The summary by CVE is:
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.
The weakness was presented 06/06/2014 (Website). It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2013-0250 since 12/06/2012. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 2.0.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Secunia (SA52037†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: InitializationCWE: CWE-665
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Corosync 2.0.1
Patch: github.com
Timeline
12/06/2012 🔍02/04/2013 🔍
06/06/2014 🔍
06/06/2014 🔍
03/26/2015 🔍
03/22/2022 🔍
Sources
Product: github.comAdvisory: b3f456a8ceefac6e9f2e9acc2ea0c159d412b595
Status: Not defined
Confirmation: 🔍
CVE: CVE-2013-0250 (🔍)
GCVE (CVE): GCVE-0-2013-0250
GCVE (VulDB): GCVE-100-69963
Secunia: 52037 - Corosync HMAC Initialization Denial of Service Vulnerability, Moderately Critical
Entry
Created: 03/26/2015 12:07Updated: 03/22/2022 12:40
Changes: 03/26/2015 12:07 (50), 03/10/2019 15:36 (2), 03/22/2022 12:40 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.