CVE-2018-6499
No exploitation reported by the sources we read.
- Published2018-08-30
- WeaknessCWE-94
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Remote Code Execution in the following products Hybrid Cloud Management Containerized Suite HCM2017.11, HCM2018.02, HCM2018.05, Operations Bridge Containerized Suite 2017.11, 2018.02, 2018.05, Data Center Automation Containerized Suite 2017.01 until 2018.05, Service Management Automation Suite 2017.11, 2018.02, 2018.05, Service Virtualization (SV) with floating licenses using Any version using APLS older than 10.7, Unified Functional Testing (UFT) with floating licenses using Any version using APLS older than 10.7, Network Virtualization (NV) with floating licenses using Any version using APLS older than 10.7 and Network Operations Management (NOM) Suite CDF 2017.11, 2018.02, 2018.05 will allow Remote Code Execution.
Timeline
dates in UTC- 2018-08-3021:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-6499?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-6499?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2017.1 | = 2017.01 | no fix published | NVD |
| 2017.5 | = 2017.05 | no fix published | NVD |
| 2017.8 | = 2017.08 | no fix published | NVD |
| 2017.9 | = 2017.09 | no fix published | NVD |
| 2017.11 | = 2017.11 | no fix published | NVD |
| 2018.2 | = 2018.02 | no fix published | NVD |
| 2018.5 | = 2018.05 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2017.11 | = 2017.11 | no fix published | NVD |
| 2018.2 | = 2018.02 | no fix published | NVD |
| 2018.5 | = 2018.05 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2017.11 | = 2017.11 | no fix published | NVD |
| 2018.2 | = 2018.02 | no fix published | NVD |
| 2018.5 | = 2018.05 | no fix published | NVD |
5 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- CNACVSS 3.07.1read 2026-10-23
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-94read 2026-10-23
- FIRST EPSSEPSS score2.4 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-08-30
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-6499?
Is CVE-2018-6499 actively exploited?
What is the CVSS score for CVE-2018-6499?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.