docker-library / docker-library/postgres
Critical & High Security vulnerability issue with Trivy Scan in postgres 16
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.5k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Hi Team,
Postgres 16.x and 17.x has some Critical and high vulnerability reported. Can you confirm if there are any fixes planned in pipelines or these issues are false positive.
Thanks.
Postgres 17.2:
Postgres 16.6:
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 reviewing the Trivy scan findings shown for the Postgres 16.x and 17.x images, then inspect the repository's image pipelines for how vulnerability results are handled. Done means determining whether the reported Critical and High findings are false positives or identifying the specific pipeline fixes required; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgres
- Domain
- databases, devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100