It is an open source library in java built for logging error messages in applications including networks, cloud computing services.
This library has been used in many java programs designed for server as well as client applications.
What is Log4Shell in Log4j?
Log4Shell is a vulnerability that affects the core function of log4j. This allows the attacker to execute the code remotely leading to:
- Taking the complete control of the system
- Ability to test and run any code without being caught
- Acquiring the important data present in the system
- Power to delete or eject viruses inside the system files
This vulnerability is having a CVSS score of 10, stating that it’s severe in nature. Fixing of this vulnerability cannot be avoided at any cost if you are using Log4j.
Is your software under threat?
This basically depends upon the version of Log4j that you are using currently.
If you are using Log4j v1 then the risk is very lesser comparatively. Under quite certain conditions, Log4j v1 considers queries, like what we have seen affecting log4j2. These assault vectors (and conceivably others) are known to prompt remote code execution (RCE) assaults. Assuming you are utilizing a version of the Log4j v1 which has empowered JMSAppender, quite possibly you could be under threat. It is vital to remember that JMSAppender is handicapped as a matter of course and therefore it is probably not going to be permitted in many Log4j v1 using applications.
If you are Log4j v2 then the probability of risk is very higher. It is highly recommended to upgrade to the latest version in which this vulnerability is tackled.
It is important to prioritize the Log4Shell vulnerability and solve it as quickly as possible. It’s not just about proactively and consequently fixing the vulnerabilities for the developers yet in addition about having the accountability of the security issues across all of your source code storehouses including those old projects which someone will rarely use.