RocketChat / RocketChat/Docker.Official.Image
Security Scan. Critical Issues in used base image
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 337
- Forks
- 228
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 5
Description
We do automated security scans in our k8s cluster and the rocket.chat docker throws critical securing issues, coming from vulnerable packages used in the underlying base Linux image (Debian) this is also the case for latest builds (6days ago) rocket.chat Image 4.8.6
One example debians dpkg is installed in version 1.20.9 which is vulnerable and fixed in version 1.20.10
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
Start by locating the Docker build entry point and checking the Debian base image and package versions against the reported scan. Done means the image no longer contains the reported vulnerable package versions and a current image build or scan confirms the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100