Hosting request for Black Duck Security Scan Plugin

[zaman-akib]

Repository URL

https://github.com/blackduck-inc/blackduck-security-scan-plugin

New Repository Name

blackduck-security-scan-plugin

Description

Black Duck Security Scan for Jenkins

Black Duck Security Scan Plugin for Jenkins provides the functionality to configure Jenkins pipeline to run Black Duck security scan and take action on the results. Black Duck Security Scan leverages Bridge CLI, allowing you to run tests for several Black Duck products from the command line. This plugin supports FreeStyle, Pipeline and Multibranch Pipeline job types.

Black Duck Security Scan will use the following Black Duck products leveraging Bridge CLI -

1. Polaris
2. Blackducksca
3. Coverity
4. Software Risk Manager (SRM)

Currently we have a similar kind of plugin in Jenkins marketplace - https://plugins.jenkins.io/synopsys-security-scan/ which we will deprecate after releasing this new plugin as we are be re-branding the Synopsys products as Black Duck products.

GitHub users to have commit permission

@sig-tithi @zaman-akib @jahid1209 @sadmananik @maksudur-rahman-maruf @gouravjblackduck @siyaramblackduck @lsynopsys @kiransynopsys

Jenkins project users to have release permission

bd_tithi zaman_akib jahid1209 sadman_anik maksud_rahman gouravjblackduck siyaramblackduck

Issue tracker

GitHub issues

[github-actions[bot]]

Hello from your friendly Jenkins Hosting Checker

It appears you have some issues with your hosting request. Please see the list below and correct all issues marked Required. Your hosting request will not be approved until these issues are corrected. Issues marked with Warning or Info are just recommendations and will not stall the hosting process.

• :no_entry: Required: Your baseline specified does not meet the minimum Jenkins version required, please update <jenkins.version>2.401.3</jenkins.version> to at least 2.440.3 in your pom.xml. Take a look at the baseline recommendations.
• :no_entry: Required: The parent pom version '4.73' should be at least '4.85' or higher.
• :no_entry: Required: The following usernames in 'Jenkins project users to have release permission' need to log into Jira: bd_tithi, gouravjblackduck, siyaramblackduck (reports are re-synced hourly, wait to re-check for a bit after logging in)
• :no_entry: Required: The following usernames in 'Jenkins project users to have release permission' need to log into Artifactory: bd_tithi (reports are re-synced hourly, wait to re-check for a bit after logging in)
• :no_entry: Required: The dependency org.apache.httpcomponents.client5:httpclient5 should be replaced with a dependency to the api plugin io.jenkins.plugins:apache-httpcomponents-client-5-api

You can re-trigger a check by editing your hosting request or by commenting /hosting re-check

[jenkins-cert-app]

Security audit, information and commands

The security team is auditing all the hosting requests, to ensure a better security by default.

This message informs you that a Jenkins Security Scan was triggered on your repository. It takes ~10 minutes to complete.

Commands

The bot will parse all comments, and it will check if any line start with a command. Security team only:

• /audit-ok => the audit is complete, the hosting can continue :tada:.
• /audit-skip => the audit is not necessary, the hosting can continue :tada:.
• /audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

• /request-security-scan => the findings from the Jenkins Security Scan were corrected, this command will re-scan your repository :mag:.
• /audit-review => the findings from the audit were corrected, this command will ping the security team to review the findings :eyes:. It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.29.12)

[jenkins-cert-app]

The Jenkins Security Scan discovered 3 finding(s) :mag:.

Please follow the instructions below for every identified issues:

• Implement the recommended fix to address the issue.
• If you think it's a false positive, suppress the warning directly within the code.
• Alternative, you write an explanation here about why you think it's irrelevant. That will require a manual review, leading to a slower process.

After addressing the findings through one of the above methods:

• If all modifications have been made to the code, please initiate a new security scan by triggering the /request-security-scan command.
• If there are any unresolved findings (those not corrected or suppressed), request a review from the Jenkins security team by using the /audit-review command.

---

Stapler: Missing POST/RequirePOST annotation

You can find detailed information about this finding here.

ScannerGlobalConfig.java#283

``` Potential CSRF vulnerability: If ScannerGlobalConfig#doFillCoverityCredentialsIdItems connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST ```

ScannerGlobalConfig.java#279

``` Potential CSRF vulnerability: If ScannerGlobalConfig#doFillPolarisCredentialsIdItems connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST ```

ScannerGlobalConfig.java#275

``` Potential CSRF vulnerability: If ScannerGlobalConfig#doFillBlackDuckSCACredentialsIdItems connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST ```