Monday, February 10, 2025
HomeCVE/vulnerabilityRCE Bug in ZOHO Products Let Hackers Execute Arbitrary Code Remotely

RCE Bug in ZOHO Products Let Hackers Execute Arbitrary Code Remotely

Published on

SIEM as a Service

Follow Us on Google News

CISA’s bug catalog has been updated with a new vulnerability related to Java deserialization, which has been exploited in the wild by malicious threat actors. As this vulnerability affects multiple Zoho ManageEngine products that are affected.

CVE-2022-35405 has been assigned to this vulnerability and is exploitable via low-complexity attacks that do not require the interaction of the user. 

Affected Products

Using this vulnerability, attackers can gain remote code execution (RCE) on servers running the following vulnerable Zoho products:-

  • Zoho ManageEngine PAM360 (Fixed version 5510
  • Password Manager Pro (Fixed version 12101)
  • Manager Plus (Fixed version 4303)

There have been two PoC exploits available online since the start of August in the form of a Metasploit module and exploit code. This vulnerability can be exploited with the aid of a publicly available proof of concept.

Since this exploit has been included in CISA’s KEV catalog, all FCEB agencies are now being urged to update their systems against it as soon as possible.

In order to make sure that the networks of federal agencies are protected from potential attacks, the agencies have three weeks, until October 13th, to do so.

How do you find impacted installation and mitigate it?

If you are interested in finding out whether your installation has been affected, then you have to follow the steps mentioned below:-

  • First of all, go to <PMP/PAM360/AMP_Installation_Directory>/logs
  • Then you have to open the access_log_<Date>.txt file
  • Now in the text file you have to search for the keyword /xmlrpc POST. 
  • You do not need to worry if you do not find this keyword in your environment. 
  • In the event that it is present, the next step will be to proceed with it.
  • It is recommended that you search the logs files for the following line. You should take action if it exists in your installation, but if it does not, then ignore it:-

[/xmlrpc-<RandomNumbers>_###_https-jsse-nio2-<YourInstallationPort>-exec-<RandomNumber>] ERROR org.apache.xmlrpc.server.XmlRpcErrorLogger – InvocationTargetException: java.lang.reflect.InvocationTargetException

  • In the event that your machine has been compromised, you must disconnect it and isolate it from the network.
  • It is then necessary to create a zip file consisting of all the log files associated with the application.
  • Once you have done this, you can send them to the email addresses of the product support team.

There are many reasons why the U.S. cybersecurity agency has strongly urged all organizations worldwide to patch this bug on a priority basis, regardless of whether BOD 22-01 is an application that only applies to the US FCEB agencies.

Moreover, all the future vulnerabilities that meet the specified criteria will be added to the CISA Catalog in the future.

Download Free SWG – Secure Web Filtering – E-book

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Tor Browser 14.0.6 Released, What’s New!

The Tor Project has officially unveiled Tor Browser 14.0.6, now accessible for download from the...

Hackers Exploit AnyDesk Vulnerability to Gain Admin Access – PoC Released

A newly discovered vulnerability in AnyDesk, the popular remote desktop software, has sparked serious...

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Hackers Exploit AnyDesk Vulnerability to Gain Admin Access – PoC Released

A newly discovered vulnerability in AnyDesk, the popular remote desktop software, has sparked serious...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...