{"published": "2008-07-08T00:00:00", "id": "SMNTC-30082", "cvss": {"score": 0.0, "vector": "NONE"}, "history": [{"differentElements": ["description", "href", "affectedSoftware"], "edition": 1, "lastseen": "2016-09-04T11:43:34", "bulletin": {"published": "2008-07-08T00:00:00", "href": "https://www.symantec.com/security_response/vulnerability.jsp?bid=30082", "cvss": {"score": 0.0, "vector": "NONE"}, "reporter": "Symantec Security Response", "history": [], "description": "### Description\n\nMicrosoft SQL Server is prone to a remote memory-corruption vulnerability because it fails to perform adequate boundary checks on user-supplied input. Authenticated attackers can exploit this issue to execute arbitrary code and completely compromise affected computers. Failed attacks will likely cause denial-of-service conditions. \n\n### Technologies Affected\n\n * Microsoft SQL Server 2000\n * Microsoft SQL Server 2000 Desktop Engine\n * Microsoft SQL Server 2000 Desktop Engine SP1\n * Microsoft SQL Server 2000 Desktop Engine SP2\n * Microsoft SQL Server 2000 Desktop Engine SP3\n * Microsoft SQL Server 2000 Desktop Engine SP4\n * Microsoft SQL Server 2000 Itanium Edition\n * Microsoft SQL Server 2000 Itanium Edition SP1\n * Microsoft SQL Server 2000 Itanium Edition SP2\n * Microsoft SQL Server 2000 Itanium Edition SP3\n * Microsoft SQL Server 2000 Itanium Edition SP4\n * Microsoft SQL Server 2000 SP1\n * Microsoft SQL Server 2000 SP2\n * Microsoft SQL Server 2000 SP3\n * Microsoft SQL Server 2000 SP4\n * Microsoft Windows 2000 Advanced Server SP4\n * Microsoft Windows 2000 Datacenter Server SP4\n * Microsoft Windows 2000 Professional SP4\n * Microsoft Windows 2000 Server SP4\n * VMWare Vcenter Update Manager 1.0\n * VMWare Vcenter Update Manager 4.0\n * VMWare Vcenter Update Manager 4.1\n * VMWare VirtualCenter 2.5\n * VMWare VirtualCenter 2.5 Update 1\n * VMWare VirtualCenter 2.5 Update 2\n * VMWare VirtualCenter 2.5 Update 4\n * VMWare VirtualCenter 2.5 Update 5\n * VMWare VirtualCenter 2.5 Update 6\n * VMWare VirtualCenter 2.5.Update 3 Build 11983\n * VMWare vCenter 4.0\n * VMWare vCenter 4.1\n\n### Recommendations\n\n#### Disallow anonymous access to services. Permit access for trusted individuals only.\n\nPermitting access only for trusted individuals will greatly reduce the likelihood of attacks.\n\n#### Run all software as a nonprivileged user with minimal access rights.\n\nTo mitigate the impact of a successful exploit, run the affected application as a user with minimal access rights.\n\n#### Deploy network intrusion detection systems to monitor network traffic for malicious activity.\n\nDeploy NIDS to monitor network traffic for signs of suspicious or anomalous activity. This may help detect malicious actions that an attacker may take after successfully exploiting vulnerabilities in applications. Review all applicable logs regularly.\n\n#### Implement multiple redundant layers of security.\n\nSince this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploit attempts of memory-corruption vulnerabilities. \n\nThe vendor has released an advisory and fixes. Please see the references for more information. \n", "bulletinFamily": "software", "viewCount": 0, "cvelist": [], "affectedSoftware": [{"version": "4", "name": "VMWare VirtualCenter 2.5 Update", "operator": "eq"}, {"version": "2000 SP3", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "SP4", "name": "Microsoft Windows 2000 Advanced Server", "operator": "eq"}, {"version": "4.0", "name": "VMWare vCenter", "operator": "eq"}, {"version": "SP2", "name": "Microsoft SQL Server 2000 Desktop Engine", "operator": "eq"}, {"version": "2.5", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "1.0", "name": "VMWare Vcenter Update Manager", "operator": "eq"}, {"version": "SP3", "name": "Microsoft SQL Server 2000 Itanium Edition", "operator": "eq"}, {"version": "SP4", "name": "Microsoft Windows 2000 Server", "operator": "eq"}, {"version": "SP4", "name": "Microsoft Windows 2000 Datacenter Server", "operator": "eq"}, {"version": "SP4", "name": "Microsoft SQL Server 2000 Desktop Engine", "operator": "eq"}, {"version": "2000 SP4", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "1", "name": "VMWare VirtualCenter 2.5 Update", "operator": "eq"}, {"version": "4.1", "name": "VMWare Vcenter Update Manager", "operator": "eq"}, {"version": "2000 SP2", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "SP3", "name": "Microsoft SQL Server 2000 Desktop Engine", "operator": "eq"}, {"version": "2000", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "SP4", "name": "Microsoft SQL Server 2000 Itanium Edition", "operator": "eq"}, {"version": "SP4", "name": "Microsoft Windows 2000 Professional", "operator": "eq"}, {"version": "5", "name": "VMWare VirtualCenter 2.5 Update", "operator": "eq"}, {"version": "11983", "name": "VMWare VirtualCenter 2.5.Update 3 Build", "operator": "eq"}, {"version": "2000 SP1", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "4.1", "name": "VMWare vCenter", "operator": "eq"}, {"version": "6", "name": "VMWare VirtualCenter 2.5 Update", "operator": "eq"}, {"version": "SP2", "name": "Microsoft SQL Server 2000 Itanium Edition", "operator": "eq"}, {"version": "2", "name": "VMWare VirtualCenter 2.5 Update", "operator": "eq"}, {"version": "4.0", "name": "VMWare Vcenter Update Manager", "operator": "eq"}, {"version": "SP1", "name": "Microsoft SQL Server 2000 Desktop Engine", "operator": "eq"}, {"version": "SP1", "name": "Microsoft SQL Server 2000 Itanium Edition", "operator": "eq"}], "type": "symantec", "hash": "34819bfc22781b8201187a8ddebef27940acfada8cdc834b6e77ff19fecf098c", "references": [], "enchantments": {"score": {"value": 6.5, "modified": "2016-09-04T11:43:34"}}, "title": "Microsoft SQL Server Convert Function Remote Memory Corruption Vulnerability", "id": "SMNTC-30082", "lastseen": "2016-09-04T11:43:34", "edition": 1, "objectVersion": "1.2", "hashmap": [{"hash": "e1d6e318fcbf36b063eb05ebd1439150", "key": "modified"}, {"hash": "e1d6e318fcbf36b063eb05ebd1439150", "key": "published"}, {"hash": "00434175f72faf36e409dbf615c950fa", "key": "href"}, {"hash": "d41d8cd98f00b204e9800998ecf8427e", "key": "references"}, {"hash": "52e3bbafc627009ac13caff1200a0dbf", "key": "type"}, {"hash": "f9fa10ba956cacf91d7878861139efb9", "key": "bulletinFamily"}, {"hash": "d41d8cd98f00b204e9800998ecf8427e", "key": "cvelist"}, {"hash": "ab15c354a4283f1cc39b6d5ad7f7d94e", "key": "affectedSoftware"}, {"hash": "8cd4821cb504d25572038ed182587d85", "key": "cvss"}, {"hash": "9a6e8af424df11e0232b4902fda37ee0", "key": "title"}, {"hash": "c4480aaf3a9828bb91f6091e26052c79", "key": "description"}, {"hash": "d6218597dc7a1b025a781373296b2b63", "key": "reporter"}], "modified": "2008-07-08T00:00:00"}}], "description": "### Description\n\nMicrosoft SQL Server is prone to a remote memory-corruption vulnerability because it fails to perform adequate boundary checks on user-supplied input. Authenticated attackers can exploit this issue to execute arbitrary code and completely compromise affected computers. Failed attacks will likely cause denial-of-service conditions.\n\n### Technologies Affected\n\n * Microsoft SQL Server 2000 \n * Microsoft SQL Server 2000 Desktop Engine \n * Microsoft SQL Server 2000 Desktop Engine SP1 \n * Microsoft SQL Server 2000 Desktop Engine SP2 \n * Microsoft SQL Server 2000 Desktop Engine SP3 \n * Microsoft SQL Server 2000 Desktop Engine SP4 \n * Microsoft SQL Server 2000 Itanium Edition \n * Microsoft SQL Server 2000 Itanium Edition SP1 \n * Microsoft SQL Server 2000 Itanium Edition SP2 \n * Microsoft SQL Server 2000 Itanium Edition SP3 \n * Microsoft SQL Server 2000 Itanium Edition SP4 \n * Microsoft SQL Server 2000 SP1 \n * Microsoft SQL Server 2000 SP2 \n * Microsoft SQL Server 2000 SP3 \n * Microsoft SQL Server 2000 SP4 \n * Microsoft Windows 2000 Advanced Server SP4 \n * Microsoft Windows 2000 Datacenter Server SP4 \n * Microsoft Windows 2000 Professional SP4 \n * Microsoft Windows 2000 Server SP4 \n * VMWare Vcenter Update Manager 1.0 \n * VMWare Vcenter Update Manager 4.0 \n * VMWare Vcenter Update Manager 4.1 \n * VMWare VirtualCenter 2.5 \n * VMWare VirtualCenter 2.5 Update 1 \n * VMWare VirtualCenter 2.5 Update 2 \n * VMWare VirtualCenter 2.5 Update 4 \n * VMWare VirtualCenter 2.5 Update 5 \n * VMWare VirtualCenter 2.5 Update 6 \n * VMWare VirtualCenter 2.5.Update 3 Build 11983 \n * VMWare vCenter 4.0 \n * VMWare vCenter 4.1 \n\n### Recommendations\n\n**Disallow anonymous access to services. Permit access for trusted individuals only.** \nPermitting access only for trusted individuals will greatly reduce the likelihood of attacks.\n\n**Run all software as a nonprivileged user with minimal access rights.** \nTo mitigate the impact of a successful exploit, run the affected application as a user with minimal access rights.\n\n**Deploy network intrusion detection systems to monitor network traffic for malicious activity.** \nDeploy NIDS to monitor network traffic for signs of suspicious or anomalous activity. This may help detect malicious actions that an attacker may take after successfully exploiting vulnerabilities in applications. Review all applicable logs regularly.\n\n**Implement multiple redundant layers of security.** \nSince this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploit attempts of memory-corruption vulnerabilities.\n\nThe vendor has released an advisory and fixes. Please see the references for more information.\n", "hash": "85e127dc11027255e7101bd1f3a9517015386e5d4c721d87fe28321f90c27814", "enchantments": {"score": {"value": 7.5, "vector": "NONE"}, "dependencies": {"references": [], "modified": "2018-03-13T12:07:43"}, "vulnersScore": 7.5}, "type": "symantec", "lastseen": "2018-03-13T12:07:43", "edition": 2, "title": "Microsoft SQL Server Convert Function Remote Memory Corruption Vulnerability", "href": "https://www.symantec.com/content/symantec/english/en/security-center/vulnerabilities/writeup.html/30082", "modified": "2008-07-08T00:00:00", "bulletinFamily": "software", "viewCount": 1, "cvelist": [], "affectedSoftware": [{"version": "2.5 Update 1 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2000 SP1 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Desktop Engine SP1 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Desktop Engine SP3 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Desktop Engine SP2 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "1.0 ", "name": "VMWare Vcenter Update Manager", "operator": "eq"}, {"version": "2000 Itanium Edition SP1 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2.5 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2.5 Update 2 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2000 Itanium Edition SP2 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Datacenter Server SP4 ", "name": "Microsoft Windows", "operator": "eq"}, {"version": "2.5 Update 5 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "4.0 ", "name": "VMWare vCenter", "operator": "eq"}, {"version": "2000 Server SP4 ", "name": "Microsoft Windows", "operator": "eq"}, {"version": "2000 Professional SP4 ", "name": "Microsoft Windows", "operator": "eq"}, {"version": "2000 Itanium Edition SP3 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Advanced Server SP4 ", "name": "Microsoft Windows", "operator": "eq"}, {"version": "4.1 ", "name": "VMWare vCenter", "operator": "eq"}, {"version": "2000 Desktop Engine ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 SP2 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "4.0 ", "name": "VMWare Vcenter Update Manager", "operator": "eq"}, {"version": "2000 Desktop Engine SP4 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2.5 Update 4 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2.5 Update 6 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2000 SP4 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2.5.Update 3 Build 11983 ", "name": "VMWare VirtualCenter", "operator": "eq"}, {"version": "2000 SP3 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "2000 Itanium Edition SP4 ", "name": "Microsoft SQL Server", "operator": "eq"}, {"version": "4.1 ", "name": "VMWare Vcenter Update Manager", "operator": "eq"}, {"version": "2000 Itanium Edition ", "name": "Microsoft SQL Server", "operator": "eq"}], "references": [], "reporter": "Symantec Security Response", "hashmap": [{"hash": "ef47df87acea99e3eb26f43beadbce78", "key": "affectedSoftware"}, {"hash": "f9fa10ba956cacf91d7878861139efb9", "key": "bulletinFamily"}, {"hash": "d41d8cd98f00b204e9800998ecf8427e", "key": "cvelist"}, {"hash": "8cd4821cb504d25572038ed182587d85", "key": "cvss"}, {"hash": "2af288a17765c864757b6e23c113b195", "key": "description"}, {"hash": "a3c343dcbc8c0620aeefdcbbbae420e1", "key": "href"}, {"hash": "e1d6e318fcbf36b063eb05ebd1439150", "key": "modified"}, {"hash": "e1d6e318fcbf36b063eb05ebd1439150", "key": "published"}, {"hash": "d41d8cd98f00b204e9800998ecf8427e", "key": "references"}, {"hash": "d6218597dc7a1b025a781373296b2b63", "key": "reporter"}, {"hash": "9a6e8af424df11e0232b4902fda37ee0", "key": "title"}, {"hash": "52e3bbafc627009ac13caff1200a0dbf", "key": "type"}], "objectVersion": "1.3"}

{"trendmicroblog": [{"lastseen": "2018-01-09T09:54:31", "bulletinFamily": "blog", "description": "\n\nIf you read my weekly blog or follow me on [Twitter](<https://twitter.com/elisal>), you know that I\u2019m a huge sports fan. Unfortunately, when you don\u2019t live in the town of your favorite team, you can be subject to blackout rules. So, my husband and I decided to purchase NFL Sunday Ticket from DirecTV. Fast forward to a couple of years ago \u2013 I wanted to watch my team play, but the channel that the game was supposed to be on was showing another game featuring my least favorite team instead. Needless to say, I was a little upset. I called DirecTV and I wasn\u2019t shy about my feelings on the situation. The customer service representative put me on hold to figure out the problem. Why wasn\u2019t I able to see my game? The game was already over. I\u2019m sure the team at DirecTV had a big laugh over my mistake, but I owned up to it and apologized to the representative.\n\nWhen a vulnerability is submitted to the Zero Day Initiative (ZDI), the affected vendor is given 120 days to take action to patch the vulnerability. If the deadline is not met, the ZDI will publicly disclose the vulnerability in accordance with its disclosure policy. Earlier this week, the Zero Day Initiative (ZDI) published a zero-day vulnerability as a result of a vendor not patching a vulnerability. One of our internal researchers, [Ricky Lawshae](<https://twitter.com/HeadlessZeke>), submitted a vulnerability to the Zero Day Initiative in mid-June of this year involving equipment that DirecTV uses with its Wireless Genie devices. The affected equipment is a Linksys WVBR0-25 which is used as a wireless video bridge. Ricky reviewed the scripts running on the Linksys device and found one that he could to inject additional commands. He was able to implement a root shell on the box in less than 30 seconds by exploiting this command injection vulnerability, which ultimately granted him full remote unauthenticated administrator control over the device. The ZDI attempted to contact the vendor several times regarding the vulnerability but never received a reply. The ZDI informed Linksys that the vulnerability would be published on December 12, 2017. You can read [Ricky\u2019s blog](<https://www.zerodayinitiative.com/blog/2017/12/13/remote-root-in-directvs-wireless-video-bridge-a-tale-of-rage-and-despair>) to get more details on this vulnerability as well as view a video of the exploit in action.**Microsoft Update**\n\nThis week\u2019s Digital Vaccine\u00ae (DV) package includes coverage for Microsoft updates released on or before December 12, 2017. Security patches were released by Microsoft covering Internet Explorer (IE), Edge, Windows, Office, SharePoint, and Exchange. Three of the Microsoft CVEs came through the ZDI program. The following table maps Digital Vaccine filters to the Microsoft updates. Filters marked with an asterisk (*) shipped prior to this DV package, providing preemptive zero-day protection for customers. You can get more detailed information on this month\u2019s security updates from Dustin Childs\u2019 [December 2017 Security Update Review](<https://www.zerodayinitiative.com/blog/2017/12/12/the-december-2017-security-update-review>) from the Zero Day Initiative:\n\n**CVE #** | **Digital Vaccine Filter #** | **Status** \n---|---|--- \nCVE-2017-11885 | 30092 | \nCVE-2017-11886 | 30069 | \nCVE-2017-11887 | 20792 | \nCVE-2017-11888 | 30070 | \nCVE-2017-11889 | 30075 | \nCVE-2017-11890 | 30068 | \nCVE-2017-11893 | 30076 | \nCVE-2017-11894 | 30077 | \nCVE-2017-11895 | 30078 | \nCVE-2017-11899 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11901 | *29900 | \nCVE-2017-11903 | 30079 | \nCVE-2017-11905 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11906 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11907 | 30081 | \nCVE-2017-11908 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11909 | 30082 | \nCVE-2017-11910 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11911 | 30083 | \nCVE-2017-11912 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11913 | *29786 | \nCVE-2017-11914 | 30080 | \nCVE-2017-11916 | 30085 | \nCVE-2017-11918 | 30074 | \nCVE-2017-11919 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11927 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11930 | 30086 | \nCVE-2017-11932 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11934 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11935 | 30088 | \nCVE-2017-11936 | | Vendor Deemed Reproducibility or Exploitation Unlikely \nCVE-2017-11937 | 30093 | \nCVE-2017-11939 | | Vendor Deemed Reproducibility or Exploitation Unlikely \n \n \n\n**End of Support Bulletin**\n\nEarlier this week, we announced the end of support for a number of TippingPoint software releases across various models.\n\nDate of Announcement: December 12, 2017\n\n \n\nAffected IPS (N/NX-Series) TOS Versions: 3.7.0, 3.7.1, 3.7.2, 3.8.0, 3.8.1, 3.8.2, 3.8.3, 3.9.0, 3.9.1\n\nEnd of Engineering: March 31, 2018\n\nEnd of Support: December 31, 2018\n\n \n\nAffected IPS (S-Series) TOS Versions: 3.6.4, 3.6.5, 3.6.6\n\nEnd of Engineering: March 31, 2018\n\nEnd of Support: December 31, 2018\n\n \n\nAffected TPS TOS Versions: 4.0.2, 4.1.0, 4.1.1, 4.1.2, 4.2.0\n\nEnd of Engineering: March 31, 2018\n\nEnd of Support: December 31, 2018\n\n \n\nAffected SMS TOS Versions: 4.4.0\n\nEnd of Engineering: March 31, 2018\n\nEnd of Support: December 31, 2018\n\n \n\nFactory Release of TPS 5.0.0: October 16, 2017\n\nFactory Release of SMS 5.0.0: March 31, 2018\n\nFactory Release of IPS 3.8.4: March 31, 2018\n\nCustomers with any questions or need assistance with migration planning can contact the TippingPoint Technical Assistance Center. Release notes are also available on <https://tmc.tippingpoint.com>.\n\n**Zero-Day Filters**\n\nThere are no new zero-day filters in this week\u2019s Digital Vaccine (DV) package. A number of existing filters in this week\u2019s DV package were modified to update the filter description, update specific filter deployment recommendation, increase filter accuracy and/or optimize performance. You can browse the list of [published advisories](<http://www.zerodayinitiative.com/advisories/published/>) and [upcoming advisories](<http://www.zerodayinitiative.com/advisories/upcoming/>) on the [Zero Day Initiative](<http://www.zerodayinitiative.com/>) website. You can also follow the Zero Day Initiative on Twitter [@thezdi](<https://twitter.com/thezdi>) and on their [blog](<https://www.zerodayinitiative.com/blog>).\n\n**Updated Existing Zero-Day Filters**\n\nThis section highlights specific filter(s) of interest in this week\u2019s Digital Vaccine package that have been updated as a result of a vendor either issuing a patch for a vulnerability found via the Zero Day Initiative or a vulnerability that has been published by the Zero Day Initiative in accordance with its Disclosure Policy.\n\nThis week\u2019s updated zero-day filters focus on two of the vulnerabilities from this month\u2019s Microsoft update. The updated filters reflect the fact that the vulnerabilities have been published because Microsoft has issued patches for them. The dates in parentheses after each filter reflects the date we had protection in place for our customers:\n\n**_Microsoft (2)_**\n\n\u2022 29900: HTTP: Microsoft Chakra Javascript Array JIT Optimization Type Confusion Vulnerability (November 7, 2017)\n\n\u2022 29786: HTTP: Microsoft Windows VBScript VT_BSTR Use-After-Free Vulnerability (October 24, 2017)\n\n**Missed Last Week\u2019s News?**\n\nCatch up on last week\u2019s news in my [weekly recap](<http://blog.trendmicro.com/tippingpoint-threat-intelligence-zero-day-coverage-week-december-4-2017/>).", "modified": "2017-12-15T16:06:45", "published": "2017-12-15T16:06:45", "id": "TRENDMICROBLOG:83CF76ED2F779A162F6FE7688839D2BF", "href": "http://blog.trendmicro.com/tippingpoint-threat-intelligence-zero-day-coverage-week-december-11-2017/", "type": "trendmicroblog", "title": "TippingPoint Threat Intelligence and Zero-Day Coverage \u2013 Week of December 11, 2017", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}]}