Tag: rce

#log4J Log4Shell RCE 0-day exploit

If you develop software in Java, you are probably affected. Log4J is a really popular package to deal with logging.

In a nutshell, if an attacker manages to log a specific, crafted string, the library will load code from a random, remote host. Affected are all versions between 2.0 and 2.14.1.

#log4shell

Given how ubiquitous this library is, the impact of this vulnerability is quite severe. Learn how to patch it, why it’s bad, and more in this post.

Source: Log4Shell: RCE 0-day exploit found in log4j2, a popular Java logging package | LunaSec

December 10, 2021
“Secret” Agent Exposes Azure Customers To RCE

This week, again Azure makes the news with cloud security issues. Following the linked article, Microsoft secretly installed a “management agent” on customer VMs. As if the act itself was not severe enough, the agent is reachable from the network.

Source: “Secret” Agent Exposes Azure Customers To Unauthorized Code Execution | Wiz Blog

And, if this does not seem bad enough, the said agent will an attacker root access when the authentication header is missing:

This is even more severe. The RCE is the simplest RCE you can ever imagine. Simply remove the auth header and you are root. remotely. on all machines. Is this really 2021? pic.twitter.com/iIHNyqgew4
— Ami Luttwak (@amiluttwak) September 14, 2021

When working with the cloud, do your threat modelling before choosing a vendor.

September 15, 2021
For the VMware users here.

VMWare’s vCenter Server is vulnerable to a remote code execution (RCE) vulnerability. That means, an attacker would be able to execute code on any machine with that software reachable from the internet. Executing arbitrary code would also allow malware to replicate, AKA worm. The vulnerability is tracked as CVE-2021-21985.

Code execution flaw in vCenter is exploited to install web shell on unpatched machines.
From the article

Source: This is not a drill: VMware vuln with 9.8 severity rating is under attack | Ars Technica

June 5, 2021