docker-library / docker-library/ruby
GEM_HOME is world writable without enough documentation or info
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 624
- Forks
- 322
- Avg merge
- 22d 3h
- Merged PRs (30d)
- 1
Description
GEM_HOME is set to /usr/local/bundle and made world sticky + writable. This could introduce several supply-chain-related vulnerabilities and are usually harder to detect, since most scanning tools, including SBOM tools, do not collect all files. A workaround could be to encourage the use of GEM_PATH with a separate directory such as /opt/ruby-latest/bundle. Alternatively, the documentation could be updated to mention the presence of this sticky, world-writable directory in the images.
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 with the linked 3.4/slim-bookworm/Dockerfile and inspect how GEM_HOME is set and permissions are applied. Review the image documentation for GEM_HOME or GEM_PATH guidance; done should mean the chosen behavior or the sticky, world-writable directory is clearly addressed without leaving the proposed alternatives unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ruby
- Domain
- devops, documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100