Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-25878PUBLISHED: 2022-05-27
The package protobufjs before 6.11.3 are vulnerable to Prototype Pollution which can allow an attacker to add/modify properties of the Object.prototype.
This vulnerability can occur in multiple ways:
1. by providing untrusted user input to util.setProperty or to ReflectionObject.setParsedOption ...
CVE-2021-27780PUBLISHED: 2022-05-27The software may be vulnerable to both Un-Auth XML interaction and unauthenticated device enrollment.
CVE-2021-27781PUBLISHED: 2022-05-27The Master operator may be able to embed script tag in HTML with alert pop-up display cookie.
CVE-2022-1897PUBLISHED: 2022-05-27Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
CVE-2022-20666PUBLISHED: 2022-05-27
Multiple vulnerabilities in the web-based management interface of Cisco Common Services Platform Collector (CSPC) Software could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface.
These vulnerabilities are due to insufficient va...
User Rank: Apprentice
11/11/2019 | 5:24:39 PM
Anyone relying 100% upon cyber insurance for security is foolish.
Unfortunately, we are seeing more infosec professionals mistakenly use misleading and inaccurate examples of claim denials such as Sony, Mondelez, Bank of Blacksburg etcetera which did not involve stand-alone cyber policies. Other citings involve very early versions of cyber policies.
Best practice is to consider cyber insurance as the last piece of the cyber risk management puzzle. Use a broker with expertise, get multiple quotes and make sure to review the policy including conditions and exclusions. If you want to use your own IR folks, try to negotiate that into the deal.
Auto insurance is not a cure for reckless driving. The same is true for cyber insurance.