-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
False positive when resolving a version with "constraints" #442
Comments
Can you open the HTML report, expand the evidence section, and post a copy of the collected evidence? |
@jeremylong , here you are: ![]() ![]() |
As expected - this is a matching issue not a detection issue. I believe there is a similar issue raised on the core dependency-check library. The gradle plugin is scanning the correct version, but the detection engine is a little loose and is determining the wrong CPE. |
in other words - this has nothing to do with the constraints. |
ack - I swapped the numbers when doing my analysis. Apparently this is an issue with the detection. |
Thanks, @jeremylong. Any chance we can expect a fix soon? |
I do have a number of other higher priority issues with dependency-check right now. We accept PRs... |
Ok, I'll give it a try. Could you point me in the right direction on where to start? |
We are collecting the incoming from the gradle project here: Line 429 in 92cf30b
What we need to figure out is the difference between what the dependencies task is doing vs how we are pulling the information. |
We declare a constraint to use version
9.4.57.v20241219
instead of9.4.53.v20231009
for our transitive dependencies. However, the report still complains about CVEs found in the9.4.53.v20231009
.dependencies { constraints { implementation('org.eclipse.jetty:jetty-webapp:9.4.57.v20241219') } }
./gradlew dependencies
output:Build log:
The same problem is described here, but the issue is closed.
The text was updated successfully, but these errors were encountered: