flaix
commented
9 months ago A clear yes and no. Yes, but not in the near future, re all vulnerabilities. No, as in some dependencies will need more work in order to update them safely.
The thing with dependencies is that it is not always so easy to simply update to the latest version. Sometimes yes, then we can easily add that. Other times, it involves rewriting parts of the application to adapt to changed interfaces and even more testing. One problem currently is the state of the test suite and that no one went to work on it to make it stable and reliable. Which helps a lot when rewriting your code. Also some dependencies would require a newer Java version as a minimal version than we can currently support.
Often it is a simple numbers game from a tool's perspective, and I understand this from an operator's view. Just check for the version and update. But not every vulnerability in package A is a problem when used in software X, because the problematic code is never used in the software. This is the case for log4j and Gitblit, for example. But, again, I understand that these details may be important for the developer, but not the operator running many, many tools.
The latest version with updated dependencies is also available as nightly Docker container builds as gitblit/gitblit:nightly.
Gitblit 1.9.3 is difficult to deploy in production. Running grype, it returns:
I downloaded code using git clone, build it and rerun grype:
Any plan to issue a release with at least all vulnerabilities closed, or should I give up on using gitblit ?