Hosting request for Black Duck Coverity on Polaris Plugin

[zaman-akib]

Repository URL

https://github.com/blackduck-inc/blackduck-coverity-on-polaris-plugin

New Repository Name

blackduck-coverity-on-polaris-plugin

Description

Black Duck Coverity on Polaris for Jenkins simplifies implementing Coverity on Polaris static analysis in Jenkins builds.

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

GitHub users to have commit permission

@zaman-akib @blackduck-saraf @manjeet-s

Jenkins project users to have release permission

zaman_akib

Issue tracker

GitHub issues

[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.21)

[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: Repository URL 'https://github.com/blackduck-inc/blackduck-coverity-on-polaris-plugin' is not a valid GitHub repository (check that you do not have .git at the end, GitHub API doesn't support this).
• :no_entry: Required: 'New Repository Name' must end with "-plugin" (disregard if you are not requesting hosting of a plugin)
• :warning: Warning: No pom.xml detected.

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

[jenkins-cert-app]

:x: Jenkins Security Scan failed. The Security team was notified about this.

[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: The dependency org.apache.httpcomponents:httpclient should be replaced with a dependency to the api plugin org.jenkins-ci.plugins:apache-httpcomponents-client-4-api
• :no_entry: Required: The dependency org.apache.commons:commons-text should be replaced with a dependency to the api plugin io.jenkins.plugins:commons-text-api

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

[zaman-akib]

/request-security-scan

[jenkins-cert-app]

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

For every identified issue, please do one of the following:

• 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.

FreestyleCreateChangeSetFile.java#118

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

PolarisBuildStep.java#127

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

WaitForIssues.java#65

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

PolarisGlobalConfig.java#201

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

PolarisGlobalConfig.java#121

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

ExecutePolarisCliStep.java#119

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

Stapler: Missing permission check

You can find detailed information about this finding here.

FreestyleCreateChangeSetFile.java#118

``` Potential missing permission check in DescriptorImpl#doFillBuildStatusOnSkipItems ```

PolarisBuildStep.java#127

``` Potential missing permission check in DescriptorImpl#doFillPolarisCliNameItems ```

WaitForIssues.java#65

``` Potential missing permission check in DescriptorImpl#doFillBuildStatusForIssuesItems ```

ExecutePolarisCliStep.java#119

``` Potential missing permission check in DescriptorImpl#doFillPolarisCliItems ```

Jenkins: Plaintext password storage

You can find detailed information about this finding here.

FindOrInstallPolarisCli.java#34

``` Field should be reviewed whether it stores a password and is serialized to disk: proxyPassword ```

PolarisAccessTokenResolver.java#27

``` Field should be reviewed whether it stores a password and is serialized to disk: accessTokenFilePath ```

PolarisAccessTokenResolver.java#25

``` Field should be reviewed whether it stores a password and is serialized to disk: accessToken ```

PolarisServerConfig.java#44

``` Field should be reviewed whether it stores a password and is serialized to disk: accessToken ```

AccessTokenPolarisHttpClient.java#37

``` Field should be reviewed whether it stores a password and is serialized to disk: accessToken ```