-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Resolve Vulnerabilities in Runtime Image #1491
Comments
|
@pseudotensor Thanks! For certifi, then can we remove it from the filesystem during the build process? |
There are also a handful of HIGH severities, some of these may or may not be real
|
@achraf-mer Can you add the removal of pkgs folders for the h2ogpt/vllm installs like we have for DAI? |
Just randomly, @codyharris-h2o-ai For transformers, I only see 4.38.2 in the image, not 4.28.1. I don't know where it is getting the versions. |
It's picking it up from |
findings.json Search for "filePath" in the JSON |
Ok, that's old code, could be updated, not part of image really. |
@codyharris-h2o-ai I pushed those changes to remove those unnecessary files. Try again tomorrow on 0.2.0-410 |
@codyharris-h2o-ai Please check again. |
@pseudotensor thanks,
|
Sorry 512 is gradio 3 for k8 and 513 failed during push due to some network issue. Need to avoid the gradio 3 builds we make for k8 issue. |
Ok will try 410 |
I'm building new one, 414. |
I see done in 98e390b and you are building a new image, so will wait and see how to address new findings, thanks. |
@achraf-mer I already removed the items, I unassigned you thanks! |
Latest scan of 414:
wrt ray, we must mitigate the functionality by removing the offending source files in the package (such as overwriting or deleting or stubbing out the appropriate functions), or remove ray altogether. |
Where is cryptography==38.0.04 from? I only see we install any latest version, unconstrained. Should be 42.0.5. |
@pseudotensor, hey it appears to be coming from |
I think it's because docker build was using fixed miniconda version, not latest, so should be ok tomorrow. |
|
@codyharris-h2o-ai is the |
I discussed this with @YogevMaty and it sounds like it is still an issue |
Apparently this CVE is very similar to the one we had in h2o3 . what to do https://docs.ray.io/en/latest/ray-security/index.html#best-practices more info in -https://www.oligo.security/blog/shadowray-attack-ai-workloads-actively-exploited-in-the-wild |
Hello!
As part of our ongoing to ensure the security of our products, one or more vulnerabilties requiring redmediation have been identified.
To resolve this, we recommend the following approach:
trivy
(https://aquasecurity.github.io/trivy)trivy image --scanners vuln --severity CRITICAL,HIGH --timeout 60m [...image address...]
trivy
. The provided scans were taken using a different scanner (ECR), so the first step should be to validate thattrivy
can see them as well.trivy
enables you to scan the image without pushing them, so it should help in finding the resolutionNote that we disregard the severity levels assigned by various tools and operate soley on CVSS in line with NIST guidelines. Also note that this scan was performed by ECR, so the results will likely be different. It is in our experience that Trivy produces more results than ECR or Prisma.
The text was updated successfully, but these errors were encountered: