Cisco NX-OS 5.0/5.1 on Nexus 5000 igmp_snoop_orib_fill_source_update memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $25k-$100k | 0.00 |
Summary
A vulnerability was found in Cisco NX-OS 5.0/5.1 on Nexus 5000. It has been classified as problematic. This vulnerability affects the function igmp_snoop_orib_fill_source_update. The manipulation leads to memory corruption.
This vulnerability is listed as CVE-2012-1357. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Cisco NX-OS 5.0/5.1 on Nexus 5000 (Router Operating System) and classified as problematic. This issue affects the function igmp_snoop_orib_fill_source_update. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is availability. The summary by CVE is:
The igmp_snoop_orib_fill_source_update function in the IGMP process in NX-OS 5.0 and 5.1 on Cisco Nexus 5000 series switches allows remote attackers to cause a denial of service (device reload) via IGMP packets, aka Bug ID CSCts46521.
The weakness was presented 08/06/2012 with Cisco (Website). The advisory is shared at cisco.com. The identification of this vulnerability is CVE-2012-1357 since 02/27/2012. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 05/04/2019).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (77464), SecurityFocus (BID 54825†) and Vulnerability Center (SBV-36313†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.cisco.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: Memory corruptionCWE: CWE-119
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/27/2012 🔍06/08/2012 🔍
08/06/2012 🔍
08/06/2012 🔍
08/06/2012 🔍
10/02/2012 🔍
03/23/2015 🔍
05/04/2019 🔍
Sources
Vendor: cisco.comAdvisory: cisco.com
Organization: Cisco
Status: Not defined
Confirmation: 🔍
CVE: CVE-2012-1357 (🔍)
GCVE (CVE): GCVE-0-2012-1357
GCVE (VulDB): GCVE-100-61493
X-Force: 77464
SecurityFocus: 54825 - Multiple Cisco Nexus Devices CVE-2012-1357 Remote Denial of Service Vulnerability
Vulnerability Center: 36313 - Cisco NX-OS 5.0-5.1(2) on Nexus 5000 Remote Denial of Service via IGMP Packets, High
Entry
Created: 03/23/2015 16:50Updated: 05/04/2019 19:10
Changes: 03/23/2015 16:50 (50), 05/04/2019 19:10 (11)
Complete: 🔍
Cache ID: 216:051:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.