CVE-2018-15427 json
Cisco Video Surveillance Manager Appliance Default Password Vulnerability
published 8y ago modified 4mo ago also EUVD-2018-7305
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.8%
- EPSS 6.8% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
A vulnerability in Cisco Video Surveillance Manager (VSM) Software running on certain Cisco Connected Safety and Security Unified Computing System (UCS) platforms could allow an unauthenticated, remote attacker to log in to an affected system by using the root account, which has default, static user credentials. The vulnerability is due to the presence of undocumented, default, static user credentials for the root account of the affected software on certain systems. An attacker could exploit this vulnerability by using the account to log in to an affected system. A successful exploit could allow the attacker to log in to the affected system and execute arbitrary commands as the root user.
Is CVE-2018-15427 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
6.83% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Cisco Cisco Video Surveillance Manager
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
tools.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180921-vsm
vendor-advisory
-
securityfocus.com
/bid/105381
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1041733
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-15427
- NVD CVE-2018-15427
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.