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

Vulnerability patch in hub #2269

Closed
wants to merge 1 commit into from
Closed

Vulnerability patch in hub #2269

wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Jun 22, 2021

A rebuild of jupyterhub/k8s-hub has been found to influence the detected vulnerabilities! This PR will trigger a rebuild because it has updated a comment in the Dockerfile.

About

This scan for known vulnerabilities has been made by aquasecurity/trivy. Trivy was configured to filter the vulnerabilities with the following settings:

  • ignore-unfixed: true

Before

Before trying to rebuild the image, the following vulnerabilities was detected in jupyterhub/k8s-hub:1.0.1.

Target Vuln. ID Package Name Installed v. Fixed v.
ubuntu CVE-2021-3580 libhogweed5 3.5.1+really3.5.1-2ubuntu0.1 3.5.1+really3.5.1-2ubuntu0.2
ubuntu CVE-2021-3580 libnettle7 3.5.1+really3.5.1-2ubuntu0.1 3.5.1+really3.5.1-2ubuntu0.2

After

Target Vuln. ID Package Name Installed v. Fixed v.
ubuntu CVE-2021-3520 liblz4-1 1.9.2-2 1.9.2-2ubuntu0.20.04.1
ubuntu CVE-2021-3580 libhogweed5 3.5.1+really3.5.1-2ubuntu0.1 3.5.1+really3.5.1-2ubuntu0.2
ubuntu CVE-2021-3580 libnettle7 3.5.1+really3.5.1-2ubuntu0.1 3.5.1+really3.5.1-2ubuntu0.2

@github-actions github-actions bot added the image:rebuild-to-patch-vuln Image rebuild to patch a known external vulnerability label Jun 22, 2021
@github-actions github-actions bot force-pushed the vuln-scan-hub branch 4 times, most recently from 954bdf2 to 7f4f3a7 Compare June 27, 2021 01:07
@consideRatio
Copy link
Member

I'm so confused about this. Why does it find there to be a difference?

@github-actions github-actions bot force-pushed the vuln-scan-hub branch 2 times, most recently from 2b0a18a to c150dcc Compare June 29, 2021 00:58
@yuvipanda
Copy link
Collaborator

I see a force push - maybe whatever had to be upgraded was upgraded in a separate PR somehow?

@consideRatio
Copy link
Member

I'm generally clueless. The force push happens when it re-checks even though it is the same changes etc as it was before I think. I'm quite confused about the PR creation action. Besides the PR creation action, I think it is veeeery weird that the first scan on the existing image finds one less vulnerability than on the freshly built image - i have no explanation for that and I have seen it also directly after 1.0.1 was published and there were a fresh latest version etc.

@consideRatio
Copy link
Member

Closing this PR as merging #2304 made the vulnerabilities be patched.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
image:rebuild-to-patch-vuln Image rebuild to patch a known external vulnerability
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants