-
Notifications
You must be signed in to change notification settings - Fork 157
Security scanner flagging jar file for upgrade. #554
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
Comments
Hi, looking at the version number, I expects this flag is about spring framework. Nevertheless, we are working on a new release of ShinyProxy that will update all dependencies. |
I'm just trying rshinyproxy for first time. I use Trivy vulnerability scanner on my docker build pipeline. these are the CVEs
|
Most organizations have remediate policy of 10days for Critical and 30 days for High. regardless if it could never happen. |
I am pulling the shinyproxy image:
FROM openanalytics/shinyproxy:3.1.1
In a routine security scanning the scanner printed the following about the shinyproxy.jar file. I am not sure what it means. The versions clearly don't align with anything about shinyproxy releases. Is it something in the jar file or about the way it was built?
/opt/docker/overlay2/2941cc1d079118aedff759fc1910234ffb1fe3f70fb236c2df574451eb7d0390/merged/opt/shinyproxy/shinyproxy.jar
Installed version : 6.2.4
Fixed version : 6.2.7
The text was updated successfully, but these errors were encountered: