GEM_HOME is world writable without enough documentation or info

Open
#507 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, ruby

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.

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.

Dominant language
Shell
Stars
627
Forks
322
Avg merge
23h 39m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker-library/ruby

All issues in docker-library/ruby

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.