Remediate Security Vulnerability Findings In 1.23.2
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.5k
- Forks
- 1.8k
- Avg merge
- 42m
- Merged PRs (30d)
- 2
Description
Hello! We ran a twistlock scan and it showed the following CVE's:
libtiff5-
- CVE-2022-1210
- CVE-2022-1622
- CVE-2022-1623
- CVE-2022-2056
- CVE-2022-2057
- CVE-2022-2058
- CVE-2022-34526
- CVE-2022-1355
- CVE-2022-1354
- CVE-2022-3597
- CVE-2022-3627
- CVE-2022-3598
- CVE-2022-3626
- CVE-2022-3599
- CVE-2022-3970
- CVE-2022-3570
- CVE-2022-2869
- CVE-2022-2867
- CVE-2022-2868
libdb5.3-
libgd3-
If possible, we'd like these to be patched/remediated for compliance reasons on our end. Let me know if you need more info!
Contributor guide
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
Begin by reproducing the reported Twistlock scan for the 1.23.2 image and map the listed libtiff5, libdb5.3, and libgd3 findings to their dependency sources. Done means the listed CVEs are remediated and a subsequent scan confirms compliance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100