Apache Log4j 2
Logback
Our great sponsors
Apache Log4j 2 | Logback | |
---|---|---|
108 | 19 | |
3,259 | 2,882 | |
1.0% | 1.1% | |
9.9 | 8.7 | |
about 19 hours ago | 3 days ago | |
Java | Java | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Apache Log4j 2
-
Hackers exploited Windows 0-day for 6 months after Microsoft knew of it
I don't think that's a good example. While Apache devs are volunteers and Microsoft devs are employees, they were criticized for their slow response time and seeming lack of urgency until it was far too late.
https://github.com/apache/logging-log4j2/pull/608#issuecomme...
- The Unsung Heroes of Open Source: The Dedicated Maintainers Behind Lesser-Known Projects
-
The Dedicated Maintainers Behind Lesser-Known Open Source Projects
However, there are many open source projects that are widely used but not well-known, including cURL, ImageMagick, MyCLI, Homebrew, Apache Log4j, and OpenSSL. This article will take a closer look at these unsung heroes of the open source world. I do not want to give them a business model or financial advice in this article. This largely depends on the author's personal experience and values. I just want to raise more awareness about these open source projects.
-
Log4Shell Still Has Sting in the Tail
> When it was first revealed in early December 2021, the Log4Shell bug was described as one of the most severe security vulnerabilities ever.
> The Apache Software Foundation, which maintains the open-source tool, quickly released a patch...
Apache horribly mismanaged this and did not release a patch until it was already widely known and being exploited in the wild. They also messed up and had to release several subsequent patches to actually fix the vulnerability.
Remember: this vulnerability was disclosed to them in November.
https://github.com/apache/logging-log4j2/pull/608#issuecomme...
-
The US Cybersecurity and Infrastructure Agency open-sourced a new tool named Scuba
Think back to the Log4J event, were you affected? (https://github.com/apache/logging-log4j2)
-
5 Best Logging Solutions for Java
Log4J(https://logging.apache.org/log4j/2.x/) is a Java-based logging framework. It is a part of Apache Logging Services. It was also the most popular and widely used Java logging solution until the exposure of its Log4Shell vulnerability last year.
- GitHub’s database of security advisories is now open source
-
System Logger
Most applications currently use Log4J2 or SLF4J. Both provide a compatible System.Logger implementation.
-
Toronto paramedic union issues warning after no ambulances were available to respond to life-threatening call
In software, you can go and see exactly who did what, when. How the Log4Shell vulnerability was patched, its detailed history and can work out how long that vulnerability was there for. Same with Wikipedia, where you can see every edit and discuss those that were made. It should not take a law degree and weeks of examination to find some bullshit is being slid into a bill, this is criminal.
- Does the Heroku Ruby Stack use Log4j?
Logback
-
Logging in your API
Java -> Logback, Log4j2, JDK (Java Util Logging), Slf4j, e.t.c.
-
Spring Boot logging with Loki, Promtail, and Grafana (Loki stack)
This is a GitHub link to my demo app. It’s simple Spring Boot web app used to debugging various stuff. There are many ways to configure JSON logging in Spring Boot. I decided to use Logback because it is easy to configure and one of the most widely used logging library in the Java Community. To enable JSON logging we need to add below dependencies.
-
5 Best Logging Solutions for Java
Logback(https://logback.qos.ch/) is another non-commercial Java logging framework. It labels itself as a successor to the previously discussed Log4j framework.
-
Log4j: The Pain Just Keeps Going and Going
> Then apache decides to put new people on log4j, do a backward incompatible v2 design that nevertheless is worse than slf4j. Why?
slf4j itself isn't a logging framework. It's a facade to logging frameworks.
Simple Logging Facade for Java ( https://www.slf4j.org )
It needs a logging framework behind it - log4j, log4j2, logback, commons, JUL.
The question is "why do log4j2?"
Logback went from the log4j1.x path ( https://logback.qos.ch )
Log4j2 has a lot of features that weren't present when the project started ( https://en.wikipedia.org/wiki/Log4j#Apache_Log4j_2 ).
There is a licensing difference between Logback (LGPL) and Log4jx (Apache Commons).
-
E2E-Testing in CI Environment With Testcontainers
Also, I'd like you to pay attention to the log consumer. You see, when the E2E scenario fails, it's not always obvious why. Sometimes to understand the source of the problem you have to dig into containers' logs. Thankfully the log consumer allows us to forward a container's logs to any SLF4J logger instance. In this project, containers' logs are forwarded to regular text files (you can find the Logback configuration in the repository). Though it's much better to transfer logs to external logging facility (e.g. Kibana).
- 🛡️ This is how we maintain & release Secured Software on Github 🤖
-
How to Check if a Java Project Depends on A Vulnerable Version of Log4j
This shows that the MariaDB JDBC driver uses Logback as a logging framework. Although Logback is not affected by Log4Shell, it has a related vulnerability (of much lesser severity, no need to panic) fixed in version 1.2.8 and 1.3.0-alpha11. I checked the version used by the connector and found that it used 1.3.0-alpha10. Even though Logback is included as a test dependency in the MariaDB driver, I sent a pull request on GitHub to update it. I encourage you to do the same in any open-source project you find and that includes a vulnerable dependency.
-
Migrating off of Log4j 2.x
Dependencing on the project, changing the logger might range from easy peasy to a multi-week task. I'm ready to bet that in many (most?) cases, it'd actually be quite easy, so let's explore how to do it, using Logback as the target (there aren't that many alternatives actually).
-
Serious flaw in Java log4j has been discovered, affecting large number of devices. [weekly tech news]
Logback
-
RCE 0-day exploit found in log4j, a popular Java logging package
Also https://github.com/qos-ch/logback/commit/b810c115e363081afc70f8bf4ee535318c3a34e1
What are some alternatives?
Logbook - An extensible Java library for HTTP request and response logging
reload4j - reload4j is a drop-in replacement for log4j 1.2.17
tinylog - tinylog is a lightweight logging framework for Java, Kotlin, Scala, and Android
Logstash - Logstash - transport and process your logs, events, or other data
SLF4J - Simple Logging Facade for Java
kibana - Your window into the Elastic Stack
graylog - Free and open log management
nuclei-templates - Community curated list of templates for the nuclei engine to find security vulnerabilities.
morgan - HTTP request logger middleware for node.js