CVE-2015-0722
Published: 2015-05-25
Last Modified: 2015-05-26
CVE Author: NIST National Vulnerability Database
CVE Assigner: psirt@cisco.com
The network drivers in Cisco TelePresence T, Cisco TelePresence TE, and Cisco TelePresence TC before 7.3.2 allow remote attackers to cause a denial of service (process restart or device reload) via a flood of crafted IP packets, aka Bug ID CSCuj68952.
| Severity | High |
| Base Score | 7.8/10 |
| Exploit Score | 10/10 |
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Impact Score | 6.9/10 |
| Confidentiality Impact | None |
| Availability Impact | Complete |
| Integrity Impact | None |
| Vector String | AV:N/AC:L/Au:N/C:N/I:N/A:C |
NIST has not assigned a CVSSv3.1 Score.
| CPE | Vulnerable | Start | Excluding |
|---|---|---|---|
| cpe:2.3:a:cisco:telepresence_tc_software:5.0_base:*:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.0_base:*:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.0.2-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.3-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.4-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.7:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.0.0:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.1.1:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.1.2:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.1.2:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.2.1:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.2.3:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:7.2.1:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:7.1.1:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.3.4:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.1.4:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_te_software:6.0.2:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:3.1_base:*:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.5:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.5-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.6:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.6-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.1.2-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.1_base:*:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.1.0:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.1.1:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:7.1.3:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:7.1.4:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.1_base:*:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:3.1.5:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.2.4:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.0.2:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.0.1:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.0.1-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.0.2:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.1.0:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:7.2.0:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.3.0:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:7.3.0:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:7.3.1:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.0.3:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_te_software:6.0_base:*:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_te_software:6.0.0:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_te_software:6.0.1:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.3.1:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.3.2:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.2_base:*:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1_base:*:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.3:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.4:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:5.1.7-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.0.0-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.1.0-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.1.1-cucm:*:*:*:*: | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.2.0:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:4.2.2:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:7.1.0:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:7.1.2:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.3.3:*:*:*:*:*:*:* | Yes | - | - |
| cpe:2.3:a:cisco:telepresence_tc_software:6.1.3:*:*:*:*:*:*:* | Yes | - | - |
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20150513-t
Free Vulnerability Scanning, Assessment and Management
Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.
Frequently Asked Questions
Do you limit the number of concurrent scans?
No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.
Do you limit the number of assets?
No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.
Will I ever be charged to use the software?
No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.
What's a vulnerability?
A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)
How can you offer this for free?
We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.
Do you offer enterprise and professional support?
Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:
- Ongoing delivery
- Patches
- Bug fixes
- Updates
- Upgrades
- Technical support
- 24/7 availability
- Unlimited Incidents
- Specialty-based routing
- Multi-Channel
- Commitments
- Software certifications
- Software assurance
- SLA
Do you store my vulnerability information on your servers?
No, we don't store the information of your vulnerabilities in our servers.
What's vulnerability management?
Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.