Vulas Analysis Report

Generated at: $generatedAt

Generated for:

SpaceGroupIdArtifactIdVersion
$space.getSpaceToken() $app.getMvnGroup() $app.getArtifact() $app.getVersion()

Aggregated report: $isAggregated

#if($isAggregated)

Aggregated projects ($projects.size()): +

#end

Plugin Configuration +

#if($thresholdMet)

Analysis Result: Success +

#else

Analysis Result: Failure -

#end

#if($thresholdMet) No critical dependencies on vulnerable archives have been found (critical according to the defined threshold of "$exceptionThreshold"), no build exception is thrown.

#else One or more critical dependencies on vulnerable archives have been found (critical according to the defined threshold of $exceptionThreshold, and considering the excluded scopes and bugs). Accordingly, a build exception is thrown in order to break the current build process. Those application projects in whose context the exception threshold is violated are highlighted in red font. Please correct those dependencies in order to avoid the build exception. #end

The following table shows all archives (column #1) that are subject to a known vulnerability (column #2). Columns #3-5 list Maven application projects that have a dependency on the respective archive, click on them to see more details in the Vulas Web Frontend.

#if($isAggregated) Since this is an aggregated report, the application projects listed in the table are submodules of the project for which the report was created. #else Since this a non-aggregated report, the application project listed in the table is identical to the project for which the report was created. #end

Note that historical vulnerabilities, i.e., cases in which a previous than the used release of a library was vulnerable are skipped in this report. You can still see them in the Vulas Web frontend.

#foreach( $vul in $vulnsToReport ) #if( $vul.hasFindingsAboveThreshold() ) #else #end #end
Archive Filename (SHA1)Vulnerability (CVSS Score)Applications including vulnerable codeApplications potentially executing vulnerable codeApplications actually executing vulnerable code
Applications listed here:
depend on a vulnerable release of the respective archive (directly or transitively)
Applications listed here:
potentially execute vulnerable code of the respective archive (according to static source code analysis)
Applications listed here:
actually execute Vulnerable code of the respective archive during application tests (JUnit or integration)
$vul.filename
$vul.archiveid
#if( $vul.bug.getReference().isEmpty() ) $vul.bug.getBugId()
$vul.bug.getCvssDisplayString() #else $vul.bug.getBugId()
$vul.bug.getCvssDisplayString() #end
$vul.filename
$vul.archiveid
#if( $vul.bug.getReference().isEmpty() ) $vul.bug.getBugId()
$vul.bug.getCvssDisplayString() #else $vul.bug.getBugId()
$vul.bug.getCvssDisplayString() #end

Contact +