Address reported CVEs in Temporal UI 2.33
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
Describe the bug
There are a few security vulnerabilities being reported in the go stdlib version that the temporal UI uses. It would be ideal if Temporal UI could upgrade out of these vulnerabilities in the next version
https://nvd.nist.gov/vuln/detail/cve-2023-45288
https://nvd.nist.gov/vuln/detail/CVE-2024-24788
https://nvd.nist.gov/vuln/detail/CVE-2024-24787
To Reproduce
Pull down the temporal ui from docker
Run a grype image scan on the docker image
Expected behavior
grype scan should not report any vulnerabilities in the image
Screenshots
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Pull the Temporal UI Docker image and run the reported grype scan first, then inspect how the image's Go standard library version is selected. Confirm the affected CVEs and identify the dependency or build configuration responsible; done means the next image scan no longer reports these vulnerabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100