• September 16, 2022
  • Ryan Cribelar

September 15, 2022 – 6 Vulns Added

In this CISA KEV Breakdown, Linux takes half the show with vulnerabilities in its kernel dating back to 2013. It’s also time to erase the amount of days it has been since Stuxnet was mentioned because it is back to 0 with the addition of CVE-2010-2568. Finally, a 0-day was discovered in the wild on Trend Micro’s Apex One client. Learn more in the notable vulnerability additions down below.

wdt_ID CVE ID Vendor Software Exploitation Result Due Date EPSS Probability EPSS Percentile cvssV3 GreyNoise
1 CVE-2022-40139 Trend Micro Apex One and Apex One as a Service Remote Code Execution 10/06/2022 0 0 7.2 0 attempts
2 CVE-2013-6282 Linux Kernel Privilege Escalation 10/06/2022 0.12992 0.95442 n/a 0 attempts
3 CVE-2013-2597 Code Aurora ACDB Audio Driver Privilege Escalation 10/06/2022 0.01404 0.71309 n/a 0 attempts
4 CVE-2013-2596 Linux Kernel Privilege Escalation 10/06/2022 0.07834 0.9299 n/a 0 attempts
5 CVE-2013-2094 Linux Kernel Privilege Escalation 10/06/2022 0.03821 0.84905 n/a 0 attempts
6 CVE-2010-2568 Microsoft Windows Remote Code Execution 10/06/2022 0.9123 0.99874 n/a 0 attempts
CVE ID Vendor Software Exploitation Result Due Date EPSS Probability EPSS Percentile cvssV3 GreyNoise

Notable Vulnerability Additions

CVE-2022-40139| Apex One Improper Validation

An improper validation weakness exists in Trend Micro’s Apex One and Apex One as-a-service clients. From the Tenable advisory regarding the vulnerability, “The vulnerability exists because Apex One agents are able to download unverified components which could lead to code execution.” This is possible due to the ‘rollback’ functionality which is used to revert Apex One agents back to previous versions. Although remote execution is possible for CVE-2022-40139, it is important to note that an attacker must first obtain Apex One server admin console access in order for the exploit to be successful.

Security Advisory:


CVE-2010-2568 | Windows Shortcut Code Execution

CVE-2010-2568 is outdated, but finds its home in the KEV catalog. Date of disclosure aside, it is still possible for organizations to not only incur a vulnerability from 2010, but to still function on the Windows XP systems most vulnerable to this exploit. A Kaspersky report in 2014 suggested it was a continuing problem, and it had no problems slowing down either. A Bleepingcomputer piece from 2016 suggested CVE-2010-2568 was the most popular exploit for that year and in 2015.

With Windows XP reaching EOL, the scope on the issue has lessened and it is good to see a vulnerability such as this added to the KEV catalog. Certifying a plan of action through BOD 22-01 to rid ourselves of vulnerabilities such as CVE-2010-2568 in public and infrastructure sectors is a path forward that we should feel good about. Hopefully the other CVEs discovered in the chain will find their home in the KEV soon, as well.

Security Advisory:


To get a better understanding of each component of our Breakdown, including what we determine to be a notable release, please see our Frequently Asked Questions section below. Also be sure to follow Nucleus Security on Twitter and LinkedIn where we will be posting each time a new Breakdown is released.

← September 14, 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