Skip to content
This repository has been archived by the owner on Apr 28, 2021. It is now read-only.

microscanner scan report differs with Aqua console report #50

Open
Mel-Github opened this issue Apr 7, 2020 · 2 comments
Open

microscanner scan report differs with Aqua console report #50

Mel-Github opened this issue Apr 7, 2020 · 2 comments

Comments

@Mel-Github
Copy link

I performed a microscanner scan against one of my repository image. I notice that the MicroScanner report is differ from the report that I have registered inside the Aqua console.

I have 2 set of scan report (1 set directly from the MicroScanner output and 1 set generate from rest API). These 2 sets of report does not have any critical vulnerability, the report detected total of 5 high severity vulnerabilities.

However, once this report has been uploaded into Aqua console, the Aqua console has moved one of the high severity vulnerability into "critical" and 4 high severity vulnerabilities.

Somehow one of high vulnerability has been upgraded to "critical" inside Aqua console.

@jerbia
Copy link
Contributor

jerbia commented May 15, 2020

Hi @Mel-Github
Can you provide reproduction steps? How did you upload the report to the Aqua Console?

Would it be possible to add a screenshot of the scan results?

@Devops-continens
Copy link

Devops-continens commented May 18, 2020

Hi Jerbia

I have attached 2 documents that I have also submitted into support ticket previously. Apparently microscanner seems to "group" critical vulnerabilities under the "high" category. The attached snapshot shows the scan result using microscanner vs image scanned in Aqua CSP.
Archive.zip

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

No branches or pull requests

3 participants