syft VS Apache Log4j 2

Syft is a popular open source CLI tool created by Anchore for generating an SBOM from container images and filesystems. It’s designed to provide a catalog of dependencies for other tools to use as a data source. It supports many popular programming languages, package managers, and container image formats.

Inside of the SBOMs, we can detect a lot: https://github.com/anchore/syft#supported-ecosystems

You're right that the active/dormant detection needs to be customized per type of runtime. We cover rpm/deb, python and java with the node and others coming very soon. The compiled languages will be our main focus next. For example, Go binaries embed some dependency metadata in the binary itself.

Also related to this effort is the "in-toto" integrity chain: https://in-toto.io/in-toto/ Since we're already connecting build to run, we aim to complete the chain.

Installing syft is pretty straight forward. On any Linux/Mac environment you can run the following command to install

The data format is supported by cargo audit, Syft and Trivy. Reading it from your own tools is also very easy.

A Software-Bill-of-Materials (SBOM) lists all the software components included in an image. Buildpacks support SBOMs in CycloneDX, Syft and SPDX formats.

I think you can already do that using Syft.

I'll continue relying on Anitya for the feed and syft/grype to build my SBOM and track vulnerabilities.

Today corporations, open source projects, nonprofit foundations, and even governments are all trying to figure out how to improve the global software supply chain security. While these efforts are more than welcome, for the moment, there is hardly any straightforward way for organizations to improve on that front.

Syft is a popular open source tool that generates SBOMs for software applications and also containers. You can execute it manually and include the generated artifacts into your release, but you can also automate the process using a GitHub Action that will be triggered whenever you have a new release on your repository.

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 official website. The vulnerability was introduced in 2.0-beta7 which was released in 2013.

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.

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.

> 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...

Think back to the Log4J event, were you affected? (https://github.com/apache/logging-log4j2)