Skip to content
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

Extension does not return correct scan results on Windows 10. #77

Open
NandiniDJFrog opened this issue Jul 27, 2022 · 5 comments
Open

Comments

@NandiniDJFrog
Copy link

The Docker Desktop JFrog Extension does not work properly on Windows 10 machines. Image scans seem to be missing most or all vulnerabilities.

This problem can be demonstrated by Scanning the nginx:1.23.1 image, which is publicly available from DockerHub.

Using Artifactory 7.41.6 and Xray 3.52.4, when we scan the image nginx:1.23.1 using the "All Vulnerabilities" scanning policy, we get the following scan results.

Screen Shot 2022-07-27 at 11 51 40 AM

The count of "critical" "high" "medium" and "low" vulnerabilities matches the counts when we generate a report for each severity level for this specific image (note in the screenshot above, the count by severity is organized from top to bottom critical to low while in the screenshot below the count is organized top to bottom low to critical).

Screen Shot 2022-07-27 at 11 49 46 AM

When scanning from Windows 10 with the same settings, however, there are no vulnerabilities found at all.

Screenshot (2)

I tried using the "Watches" scanning policy instead, however this resulted in the Image scan simply failing.

@sverdlov93
Copy link
Contributor

Hi @AnandDJFrog,
Thanks for reporting this issue.
We found the cause for that problem on JFrog Xray side and it should be fixed soon.
I will update this thread once the next release will be out.

@NandiniDJFrog
Copy link
Author

@sverdlov93 Excellent, thank you for looking into this 😁

@raphaelZaa
Copy link

Hi @sverdlov93, I believe a customer is facing this issue. Has this been resolved?

@sverdlov93
Copy link
Contributor

Hi, @raphaelZaa the issue is already fixed and soon it will be released on JFrog Xray version.
I will update here the exact version number.

@raphaelZaa
Copy link

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants