-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High severity issues in security dependency check #512
Comments
Hi! It looks like this is all due to a dependency? Does that dependency have an updated version without whatever security issues? |
I'm using ktlint directly in my project, and i updated to the |
Sorry, yes I'm one of the maintainers of the project. I was just wondering if you'd looked into solutions at all. We will be releasing 0.34.0 soon and we can aim to include a fix for this. |
Thank you! |
@drcabral are this security issues raised only for latest release or releases before? And could you provide more details about this issues, like what exactly dependencies have security issues? |
Hi @Tapchicoma, I was using the version I can share with you the messages about the issues that the dependency check identified:
|
Ah ok I remember this issue. I believe the vulnerability has actually been fixed, but the process to mark it has such hasn't been resolved. @JLLeitschuh did it ever get resubmitted? |
Also should be not a problem if #451 will be resolved. |
I'm pretty unfamiliar with the process, but it does look like our assigned CVE number (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010260) does say it should be fixed in 0.30.0 and later; so not sure what's missing as far as the reporting. |
The vulnerabilities from dependencies remain. I think the easiest solution for ktlint would be to simply upgrade as much as possible to the latest version. |
Ah, I didn't see this one:
This is a bit confusing because I don't believe we actually include checkstyle as a dependency, we just output a checkstyle-formatted report. Does it just want us to require a higher checkstyle version?
|
Heh. Sent with GitHawk |
The vulnerability in ktlint itself should be resolved as of 0.30.0. That finding actually spawned this bit of research that's now public:
|
@JLLeitschuh do you know why we're getting flagged for the checkstyle vulnerability? We don't actually bring it in as a dependency. Is it just the checkstyle version we're writing out in the checkstyle reporter? |
I added the OWASP Dependency Check plugin to the project in #514 and running it directly against the project doesn‘t trigger the checkstyle vulnerability. However, there are others:
|
When we remove the MavenDependencyResolver the Guava, HttpClient and Plexus Utils dependencies will go away. #451 |
Hi. It looks like this ticket is ready to be resolved, now that #566 has been merged. Could we expect v0.35.0 soon? |
Hi everyone,
I'm working with ktlint and i checked for dependency security issues in my project. In the latest version, ktlint presents 7 high severity issues, what i think that is a lot.
Is there any work going on to take a look and solve these problems? Thanks!
Analysis made with owasp dependency check
The text was updated successfully, but these errors were encountered: