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

RStudio Workbench CVEs #681

Open
securian-bpmcd opened this issue Dec 28, 2023 · 4 comments
Open

RStudio Workbench CVEs #681

securian-bpmcd opened this issue Dec 28, 2023 · 4 comments

Comments

@securian-bpmcd
Copy link

The below CVEs affect Go 1.19. These were found by our Prisma Cloud Scan tool while scanning the current (12/27/2023) "rstudio/r-session-complete:jammy-2023.03.2" image.

CVE-2023-39323 Go
CVE-2023-29405 Go
CVE-2023-29404 Go
CVE-2023-29402 Go
CVE-2023-24540 Go
CVE-2023-24538 Go

@bschwedler
Copy link
Contributor

@securian-bpmcd Thank you for reporting these!

Do you still see these vulnerabilities in the latest image?

rstudio/r-session-complete:ubuntu2204-2024.09.0

@securian-bpmcd
Copy link
Author

@bschwedler We're using RStudio on SageMaker and the most recent version that we can use to match the AWS environment is 2024.04.2

@securian-bpmcd
Copy link
Author

The 2024.04.2 image scan reports the following CVEs:
CVE-2024-24790
CVE-2023-24540
CVE-2023-24538

@bschwedler
Copy link
Contributor

Ah, thanks for the added detail on where you are seeing this.
AWS builds and deploys the container image running in SageMaker. It starts from the public container images defined in this repository and AWS further customizes the Workbench image to add the functionality required for SageMaker.


I also want to add a little more detail around patching and rebuilding previous versions of the container images.

We are currently routinely rebuilding the most recent version of the container images to pick up OS and package security updates.

The current repository structure makes it difficult to use the same rebuild process for previous container versions. We are working to improve the workflows as well as the visibility of our internal scan results.

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

No branches or pull requests

2 participants