redhat-cop / redhat-cop/group-sync-operator
Multiple vulnerabilities in dependency kube-rbac-proxy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
The container image for kube-rbac-proxy that is included in this operator is over two years old and contains multiple vulnerabilities. Many of them are ranked as high severity. This is being flagged by our internal security tools.
See the report on Quay for specifics:
https://quay.io/repository/redhat-cop/kube-rbac-proxy/manifest/sha256:8ac4596bae29a6956d9e3a6688e38fc82ea0dbab877ab554096d54f80f0252a3?tab=vulnerabilities&fixable=true
Could you either make sure that the referenced image is updated or utilize another image that is being actively maintained?
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
No files or tests are named. Locate where the kube-rbac-proxy container image is referenced, review the linked Quay vulnerability report, and check available maintained image options. Done means the operator uses an updated or actively maintained image and the reported vulnerabilities are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100