CVSS 3.0
8.8 highCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HHigh (8.8) in cisco. EPSS 6.0% estimated probability of exploitation activity in the next 30 days.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExplain CVE-2017-6753 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-6753?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-6753?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-6753 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| cisco:webex_event_center | t30_base |
| cisco:webex_event_center | t31_base |
| cisco:webex_event_center | t32_base |
| cisco:webex_meeting_center | t30_base |
| cisco:webex_meeting_center | t31_base |
| cisco:webex_meeting_center | t32_base |
| cisco:webex_meetings | t30_base |
| cisco:webex_meetings_server | 1.1_base |
| cisco:webex_meetings_server | 1.5.1.6 |
| cisco:webex_meetings_server | 1.5.1.131 |
| cisco:webex_meetings_server | 1.5_base |
| cisco:webex_meetings_server | 2.0.1.107 |
| cisco:webex_meetings_server | 2.0_base |
| cisco:webex_meetings_server | 2.5.1.5 |
| cisco:webex_meetings_server | 2.5.1.29 |
| cisco:webex_meetings_server | 2.5.99.2 |
| cisco:webex_meetings_server | 2.5_base |
| cisco:webex_meetings_server | 2.6.0 |
| cisco:webex_meetings_server | 2.6.1.39 |
| cisco:webex_meetings_server | 2.7.1 |
| cisco:webex_meetings_server | 2.7_base |
| cisco:webex_meetings_server | 2.8_base |
| cisco:webex_meetings_server_2.0 | mr2 |
| cisco:webex_meetings_server_2.0 | mr3 |
| cisco:webex_meetings_server_2.0 | mr4 |
| cisco:webex_meetings_server_2.0 | mr5 |
| cisco:webex_meetings_server_2.0 | mr6 |
| cisco:webex_meetings_server_2.0 | mr7 |
| cisco:webex_meetings_server_2.0 | mr8 |
| cisco:webex_meetings_server_2.0 | mr9 |
| cisco:webex_meetings_server_2.0_mr8_patch | 1 |
| cisco:webex_meetings_server_2.0_mr9_patch | 1 |
| cisco:webex_meetings_server_2.0_mr9_patch | 2 |
| cisco:webex_meetings_server_2.0_mr9_patch | 3 |
| cisco:webex_meetings_server_2.5 | mr1 |
| cisco:webex_meetings_server_2.5 | mr2 |
| cisco:webex_meetings_server_2.5 | mr3 |
| cisco:webex_meetings_server_2.5 | mr4 |
| cisco:webex_meetings_server_2.5 | mr5 |
| cisco:webex_meetings_server_2.5 | mr6 |
| cisco:webex_meetings_server_2.5_mr2_patch | 1 |
| cisco:webex_meetings_server_2.5_mr5_patch | 1 |
| cisco:webex_meetings_server_2.5_mr6_patch | 1 |
| cisco:webex_meetings_server_2.5_mr6_patch | 2 |
| cisco:webex_meetings_server_2.5_mr6_patch | 3 |
| cisco:webex_meetings_server_2.5_mr6_patch | 4 |
| cisco:webex_meetings_server_2.6 | mr1 |
| cisco:webex_meetings_server_2.6 | mr2 |
| cisco:webex_meetings_server_2.6 | mr3 |
| cisco:webex_meetings_server_2.6_mr1_patch | 1 |
| cisco:webex_meetings_server_2.6_mr2_patch | 1 |
| cisco:webex_meetings_server_2.6_mr3_patch | 1 |
| cisco:webex_meetings_server_2.6_mr3_patch | 2 |
| cisco:webex_meetings_server_2.7 | mr1 |
| cisco:webex_meetings_server_2.7 | mr2 |
| cisco:webex_meetings_server_2.7_mr1_patch | 1 |
| cisco:webex_meetings_server_2.7_mr2_patch | 1 |
| cisco:webex_support_center | t30_base |
| cisco:webex_support_center | t31_base |
| cisco:webex_support_center | t32_base |
| cisco:webex_training_center | t30_base |
| cisco:webex_training_center | t31_base |
| cisco:webex_training_center | t32_base |
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).