-
Notifications
You must be signed in to change notification settings - Fork 17
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
Critical and high vulnerabilities found in latest mcr.microsoft.com/openjdk/jdk:21-mariner #113
Comments
These are refreshed weekly, so I suspect something has gone amiss here - @d3r3kk to triage. |
Hello @kropiwnickij thank you for the report. Please do note that the vulnerabilities you have discovered are handled by the Mariner team and not by the OpenJDK team. As @karianna said above, the OpenJDK team refreshes our images weekly to ensure we pick up the latest fixes from the Mariner team. Unless a vulnerability pertains to the OpenJDK itself, or any of its dependencies, we must pass the issue on to the Mariner team. To be thorough and to learn myself what the concerns were and how to resolve them, I found the following that you may find helpful.
|
@d3r3kk that you for explanation. Looking at one of CVE seems that it was solved in 1.19.4 patch in mariner, but as per NVD newer one as 1.21.3 is expected - this causes incorrect scan results. As first report shows: How do you propose to approach this case? Should this be reported to Mariner team to upgrade to latest krb version? Regards |
@kropiwnickij, thanks for your attention.
Yes, if it doesn't pertain directly to the OpenJDK itself, or the tools, libraries, and direct dependencies it adds to the image, then it goes to the Mariner team. |
Hi Team,
When running container image scans for latest jdk:21-mariner (latest as per https://mcr.microsoft.com/en-us/artifact/mar/openjdk/jdk/tags) we are seeing Critical and High vulnerabilities:
I checked that in azurelinux they were fixed in releases: https://github.com/microsoft/azurelinux/releases/tag/2.0.20241006-2.0 and https://github.com/microsoft/azurelinux/releases/tag/3.0.20240824-3.0
Is there a timeline when we can expect jdk mariner images to be refreshed and released?
Regards
Jan
The text was updated successfully, but these errors were encountered: