advisory-database
Apache Log4j 2
| advisory-database | Apache Log4j 2 | |
|---|---|---|
| 10 | 108 | |
| 1,624 | 3,278 | |
| 2.2% | 0.6% | |
| 10.0 | 9.9 | |
| 1 day ago | 1 day ago | |
| Java | ||
| Creative Commons Attribution 4.0 | Apache License 2.0 |
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.
advisory-database
- Request GitHub to build an advisory database for C / C++ packages · Issue #2963 · github/advisory-database
- Extend GitHub's CNA scope to manage CVEs for projects on GitHub
-
A CVE has been issued for hyper. Denial of Service possible
That has since been updated to Moderate: https://github.com/github/advisory-database/commit/aa9e5d5386c5610944edf2b0ee0e4301aabaf1c5
-
CVE-2022-23529 – node-jsonwebtoken
I am trying this on GitHub https://github.com/github/advisory-database/pull/1595
- CVE-2022-23529 - jsonwebtoken has insecure input validation in jwt.verify function - used by over 22,000 projects and downloaded over 36 million times per month on NPM - Exploiting the flaw could enable attackers to bypass authentication mechanisms, access confidential information etc.
-
GitHub’s database of security advisories is now open source
We already have fixed versions (where they exist) - example link below.
On backfilling the data to include advisories from before 2017 - absolutely. So far we've done this in a relatively ad-hoc way - you should already find that the most important (severe and wide-reaching) CVEs from before 2017 are in the database (and if there are any that aren't you think should be we'd love you to open an issue on the DB). We want to do a more complete backfill in the near future.
https://github.com/github/advisory-database/blob/main/adviso...
- GitHub's database of known vulnerabilities is now open source
- Security vulnerability database inclusive of CVEs and GitHub originated security advisories from the world of open source software
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...
- Create an alternative async logger implementation using JCTools
- Log4j requesting feedback on which modules/features to drop
- The Unsung Heroes of Open Source: The Dedicated Maintainers Behind Lesser-Known Projects
-
Studying Log4Shell
The official website. The vulnerability was introduced in 2.0-beta7 which was released in 2013.
-
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.
-
Apache POI Setup Logging Error
What you need is log4j-core, what you downloaded is some kind of connector between log4j and JUL. Tbh I don't know what JUL is, but that's not important. You can get log4j-core on from the official website - https://logging.apache.org/log4j/2.x/ or in maven repo. In case you're not using maven, I highly, highly recommend you using it for managing your dependencies.
-
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)
- In One Minute : log4j2
What are some alternatives?
h2 - HTTP 2.0 client & server implementation for Rust.
Logback - The reliable, generic, fast and flexible logging framework for Java.
vulndb - [mirror] The Go Vulnerability Database
reload4j - reload4j is a drop-in replacement for log4j 1.2.17
elixir-security-advisories - Public database of Elixir security advisories
tinylog - tinylog is a lightweight logging framework for Java, Kotlin, Scala, and Android
GHSA-896r-f27r-55mw
Logstash - Logstash - transport and process your logs, events, or other data
rustsec - RustSec API & Tooling
SLF4J - Simple Logging Facade for Java
napkin-math - Techniques and numbers for estimating system's performance from first-principles
kibana - Your window into the Elastic Stack