Closed vidi42 closed 3 years ago
uh not good. I think we should enable GitHub's automatic dependabot alerts for this (and all other) repositories, if possible
GitHub sends Dependabot alerts when we detect vulnerabilities affecting your repository.
@fhauptmann and @MartinWahnschaffeSymeda any comments?
Edit: GitHub seems to offer more security features, even static security analysis which might prevent things like #3578
@JonasCir Dependabot should already be enabled
Hm, then I propose to investigate why this was not caught . The CVEs are published in GitHub Advisory DB and some of them are rated as severe.
For Dependency Check false positives can be suppressed:
--suppression
as command line argument to supress false positives: https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.htmlCurrent findings not (all) fixed by #3584:
False positives:
Not exploitable:
maven-ant-tasks
is used for automating some common tasks during development.
It is not part of the release and is not relied on by the code, tests or the CI pipeline.
According to https://maven.apache.org/ant-tasks/ it has been superseded by Maven Artifact Resolver Ant Tasks.
Evaluation of findings in the comment above, to be discussed with @MartinWahnschaffeSymeda
Open findings will be addressed in new tickets (especially Keycloak 12 is not available yet): #3765, #3766
Documented all not relevant findings (https://github.com/hzi-braunschweig/SORMAS-Project/issues/3580#issuecomment-740562116) in check-suppressions.xml to exclude them in Dependency-Check on Jenkins, successfully tested.
I needed to add this argument for Dependency-Check in Jenkins, I forgot that on monday: --suppression ${WORKSPACE}/sormas-base/dependencies/check-suppressions.xml
Problem Description
The target application uses dependencies that are affected by known vulnerabilities. Applications that use dependencies which are affected by known vulnerabilities offer an additional attack surface. Known vulnerabilities could provide a generic path to compromise the application in different ways, such as extracting sensitive information, manipulating internal application states, or even compromising the underlying operating system. Depending on the vulnerability and the affected software component, they might be publicly available proof-of-concept exploits. Such vulnerabilities are very likely to be exploited, especially on services that are exposed to the Internet where the exploitation could be automated.
The following list of dependencies with known vulnerabilities has been identified:
These libraries were extracted from the release version 1.48.2 of sormas-ui, sormas-ear and sormas-rest. The current OWASP Dependency Checks also show quite a lot possible vulnarabilities (about 90) in used dependencies (java libraries).
Proposed Change
System Details
Additional information
Check this after #3449 and #3584 are done because some version updates there will resolve findings.