| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Cisco MediaSense. It has been rated as problematic. This vulnerability affects unknown code. This manipulation causes cross site scripting. This vulnerability is tracked as CVE-2014-0670. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Cisco MediaSense (version unknown). It has been declared as problematic. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in the Search and Play interface in Cisco MediaSense allows remote attackers to inject arbitrary web script or HTML via an unspecified parameter, aka Bug ID CSCum16686.
The weakness was disclosed 01/22/2014 with Cisco (Website). The advisory is shared at tools.cisco.com. This vulnerability is known as CVE-2014-0670 since 01/02/2014. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
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 (90615), SecurityFocus (BID 65053†), OSVDB (102319†) and Secunia (SA56563†). The entries VDB-66159 and VDB-66158 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
- Vendor: https://www.cisco.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
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
01/02/2014 🔍01/21/2014 🔍
01/22/2014 🔍
01/22/2014 🔍
01/23/2014 🔍
03/24/2015 🔍
01/31/2022 🔍
Sources
Vendor: cisco.comAdvisory: tools.cisco.com
Organization: Cisco
Status: Not defined
Confirmation: 🔍
CVE: CVE-2014-0670 (🔍)
GCVE (CVE): GCVE-0-2014-0670
GCVE (VulDB): GCVE-100-66157
X-Force: 90615
SecurityFocus: 65053 - Cisco MediaSense Search and Play Cross Site Scripting Vulnerability
Secunia: 56563 - Cisco MediaSense Search and Play Interface Cross-Site Scripting Vulnerability, Less Critical
OSVDB: 102319
SecurityTracker: 1029667
See also: 🔍
Entry
Created: 03/24/2015 15:54Updated: 01/31/2022 15:22
Changes: 03/24/2015 15:54 (49), 03/16/2019 10:31 (8), 01/31/2022 15:22 (3)
Complete: 🔍
Cache ID: 216::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.