September 22 – 1 New Vuln
The RCE discovered in Zoho ManageEngine affects PAM360 version 5.5 and below, and Password Manager Pro 12.1 and below, both allowing for an unauthenticated attacker to exploit. While the same vulnerability exists in Access Manager Plus 4.3 and below, authentication is required to successfully exploit the vulnerability.
| wdt_ID | CVE ID | Vendor | Software | Exploitation Result | Due Date | EPSS Probability | EPSS Percentile | cvssV3 | GreyNoise |
|---|---|---|---|---|---|---|---|---|---|
| 1 | CVE-2022-35405 | Zoho | ManageEngine | Remote Code Execution | 10/13/2022 | 0.83982 | 0.99597 | 9.8 | 2 attempts |
| CVE ID | Vendor | Software | Exploitation Result | Due Date | EPSS Probability | EPSS Percentile | cvssV3 | GreyNoise |
Notable Vulnerability Additions
CVE-2022-35405 | Zoho ManageEngine Remote Code Execution
The vulnerability was first disclosed to the vendor on June 21 by security researcher Vinicius, with CVE-2022-35405 being tagged by MITRE on July 11. The vulnerability exists due to CVE-2020-9496, a vulnerability discovered in the open-source technology Apache OFBiz, which exposes an xml-rpc endpoint which allows for RCE to occur. A working PoC as well as Metasploit module were uploaded for the vulnerability on August 2.
As early as this same day, GreyNoise sensors detected network traffic of attempted exploitation and contains an available block and reference list for GreyNoise users. At time of writing, only one other attempt has been observed since tag creation on August 2.
The advisory link below contains steps to verify if your installation has been affected by this vulnerability. To summarize:
- Navigate to <PMP/PAM360/AMP_Installation_Directory>/logs
- Open the access_log_<Date>.txt file
- Search for the keyword /xmlrpc POST in the text file. If this keyword is not found, your environment is not affected. If it is present, then proceed to the next step.
- Search for the following line in the logs files. If it is present, then your installation is compromised:
[/xmlrpc-<RandomNumbers>_###_https-jsse-nio2-<YourInstallationPort>-exec-<RandomNumber>] ERROR org.apache.xmlrpc.server.XmlRpcErrorLogger – InvocationTargetException: java.lang.reflect.InvocationTargetException
Security Advisory:
https://www.manageengine.com/products/passwordmanagerpro/advisory/cve-2022-35405.html
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 15, 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: