CVSS 3.0
7.3 highCVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:HHigh (7.3) in symantec. EPSS 21% estimated probability of exploitation activity in the next 30 days.
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:HExplain CVE-2016-2209 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2016-2209?via=ask-ai-copy and https://cve.bz/cve/CVE-2016-2209?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-2016-2209 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 |
|---|---|
| symantec:mail_security_for_microsoft_exchange | from 7.0 through 7.0.4 |
| symantec:mail_security_for_microsoft_exchange | from 7.5 through 7.5.4 |
| symantec:mail_security_for_microsoft_exchange | 6.5.8 |
| symantec:norton_power_eraser | through 5.0 |
| symantec:protection_engine | from 7.0.0 through 7.0.5 |
| symantec:protection_engine | from 7.5.0 through 7.5.4 |
| symantec:protection_engine | 7.8.0 |
| symantec:endpoint_protection | 12.1.6:mp1 |
| symantec:endpoint_protection | 12.1.6:mp1a |
| symantec:endpoint_protection | 12.1.6:mp2 |
| symantec:endpoint_protection | 12.1.6:mp3 |
| symantec:endpoint_protection | 12.1.6:mp4 |
| symantec:message_gateway | through 10.6.1-3 |
| symantec:ngc | through 22.6 |
| symantec:message_gateway_for_service_providers | 10.5 |
| symantec:message_gateway_for_service_providers | 10.6 |
| symantec:norton_bootable_removal_tool | through 2016.0 |
| symantec:mail_security_for_domino | from 8.0 through 8.0.9 |
| symantec:mail_security_for_domino | from 8.1 through 8.1.3 |
| symantec:data_center_security_server | 6.0 |
| symantec:data_center_security_server | 6.0:mp1 |
| symantec:data_center_security_server | 6.5 |
| symantec:data_center_security_server | 6.5:mp1 |
| symantec:data_center_security_server | 6.6 |
| symantec:data_center_security_server | 6.6:mp1 |
| symantec:norton_security | through 13.0.1 |
| symantec:advanced_threat_protection | through 2.0.3 |
| symantec:protection_for_sharepoint_servers | 6.03 |
| symantec:protection_for_sharepoint_servers | 6.04 |
| symantec:protection_for_sharepoint_servers | 6.05 |
| symantec:protection_for_sharepoint_servers | 6.06 |
| symantec:csapi | through 10.0.4 |
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).