October 28 – 1 New Vuln | CVE-2022-3723
In this CISA KEV Breakdown, CISA has added one vulnerability, a zero-day observed in Chrome on October 27 which has a patch released in version 107.0.5304.87 for Mac and Linux and 107.0.5304.87/.88 for Windows.
| wdt_ID | CVE ID | Vendor | Software | Exploitation Result | GreyNoise Traffic | EPSS Probability | EPSS Percentile | CVSSv3 | Due Date |
|---|---|---|---|---|---|---|---|---|---|
| 1 | CVE-2022-3723 | Chrome | Type Confusion | 0 | 0 | 0 | 0 | 11/18/2022 | |
| CVE ID | Vendor | Software | Exploitation Result | GreyNoise Traffic | EPSS Probability | EPSS Percentile | CVSSv3 | Due Date |
Notable Vulnerability Additions
CVE-2022-3723 | Chromium v8 Type Confusion
Chrome released on October 27 an emergency update to address a security bug with confirmed evidence of exploitation in the wild. Dubbed CVE-2022-3723, a type confusion vulnerability exists in the v8 JavaScript engine. Type confusion vulnerabilities exist when an object in-code does not verify the object-type upon using it in other places for other functions. This can cause for anything from code execution to crashing the service utilizing the object. Nucleus Security recommends issuing updates for Chrome browsers as soon as possible to address the security concern, as well as keeping an eye out for updates from the other popular Chromium-based browsers, such as Edge, if the problem exists outside of Google’s implementation.
Chrome users can update their browsers themselves by heading to Settings -> About Chrome, and then verifying the version implemented is the versions mentioned above, 107.0.5304.87 for Mac and Linux and 107.0.5304.87/.88 for Windows.
Security Advisory:
https://chromereleases.googleblog.com/2022/10/stable-channel-update-for-desktop_27.html
← October 25, 2022 CISA Kev Breakdown
Click here to expand our CISA KEV Breakdown Frequently Asked Questions
- What makes for a notable addition?
- A notable addition can arise from many different characteristics. If a particular vulnerability is notable to the security community or a subset of the security community or if the EPSS score reveals notable information about the vulnerability, this can constitute further analysis. It may also be the case that a particular vulnerability shines a light on everyday users and we will highlight important information and key takeaways to ensure users and readers have easy access to actionable information.
- When is the Breakdown released?
- We aim to have our analysis of each KEV update posted within 24 hours of the time in which the Catalog is updated. See CISA’s full catalog here
- I am not bound by BOD 22-01 or federal regulations, why should the KEV concern me?
- CISA encourages all organizations to utilize the Catalog as an attribute in your vulnerability prioritization framework. Organizations looking to lessen the scope on known dangerous vulnerabilities and make a goal to remediate them can understand where they currently stand against what CISA has confirmed as exploited vulnerabilities in the wild. See CISA’s section on “How should organizations use the KEV catalog?” here.
- What is EPSS?
- EPSS is the Exploit Prediction Scoring System. It is an open, data-driven effort for estimating the likelihood (probability) that a software vulnerability will be exploited in the wild. See the EPSS home page on FIRST for more information here.
- What is the difference between EPSS probability and EPSS percent?
- EPSS probability is the risk calculated by the model when determining the perceived threat of the vulnerability itself. Percentage is a relative comparison of the rest of the CVEs within the given sample. While the probability only changes upon refreshing the results from the model, the percentage can change purely based on the CVE sample given. In the case of the Breakdown, we use the percentage given by the pool of all CVEs with given EPSS data. Scores may vary post-release of the post given new information about the vulnerabilities and their perceived threat. For more information on applying and understanding EPSS data, see this article on the FIRST website, as well as their FAQ page.
- What is GreyNoise?
- GreyNoise is a platform that collects, analyzes, and labels data on IPs that scan the internet and saturate security tools with noise. Through their sensor network, GreyNoise observes vulnerability exploitation attempts for vulnerabilities that are exploited in the wild over the Internet. These are arguably vulnerabilities that should be at the very top of your priority list to remediate.
- Why are GreyNoise exploitation attempts only observed on ~20% of KEV vulnerabilities?
- Exploitation of many vulnerabilities in the CISA KEV will not be observed for many reasons that GreyNoise does a good job of explaining in this post. For example:
- The vulnerability may not be remotely exploitable
- Vulnerability exploitation may require authentication (and result in privilege escalation)
- The impacted software may not be exposed to the internet
- Mass scanning/exploitation is not occurring yet
- Exploitation of many vulnerabilities in the CISA KEV will not be observed for many reasons that GreyNoise does a good job of explaining in this post. For example: