Critical Vulnerabilities in Spring components picked up by Trivy scan
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Expected behavior
No vulnerabilities (especially high or critical severity ones) should be found on a Trivy scan
Actual behavior
Critical vulnerabilities are detected in Spring framework and other components. I'm aware of the closed issue here: https://github.com/OHDSI/WebAPI/issues/2298 and the fact the vulnerability only applies with JDK9+. This isn't really a satisfactory solution for us . Can you advise if there has been or will be a fix for this issue so that there are no critical or high severity vulnerabilities detected after scanning WebAPI installed from the latest release?
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 dependency versions included in WebAPI's latest release and reproduce the reported Trivy scan, focusing on Spring framework and other flagged components. Done means the release scan no longer reports high or critical vulnerabilities, or the remaining findings are documented with their applicability and remediation status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100