bitcoind image v27.2 contains multiple critical and high vulnerabilities
Open
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 107
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Please find more details attached.
I hope it should be possible to just rebuild current image with the latest base one.
Both v27.2 and v28.0 images were released ~6 months ago and these critical/high vulns are 4-5 months old.
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 attached bitcoind-27.2.pdf and inspect the repository's Docker image build configuration for the v27.2 and v28.0 images. Determine whether rebuilding with the current base image addresses the listed critical and high vulnerabilities, then verify the resulting image against those findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100