Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Host Perforce Static Analysis Plugin #4238

Open
michael-baron opened this issue Dec 24, 2024 · 9 comments
Open

Host Perforce Static Analysis Plugin #4238

michael-baron opened this issue Dec 24, 2024 · 9 comments
Labels
hosting-request Request to host a component in jenkinsci needs-fix security-audit-needs-correction The security audit revealed issues that must be corrected from the hosting request

Comments

@michael-baron
Copy link
Contributor

Repository URL

https://github.com/michael-baron/P4SA-Jenkins-Plugin

New Repository Name

P4SA-plugin

Description

This is a joint plugin for Perforce Static Analysis tools (Klocwork and Helix QAC). Helps automate the scans and retrieval of issue metrics for quality gating.

GitHub users to have commit permission

@michael-baron

Jenkins project users to have release permission

michael_baron

Issue tracker

GitHub issues

@michael-baron michael-baron added the hosting-request Request to host a component in jenkinsci label Dec 24, 2024
@jenkins-cert-app
Copy link
Collaborator

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 🎉.
  • /audit-skip => the audit is not necessary, the hosting can continue 🎉.
  • /audit-findings => the audit reveals some issues that require corrections ✏️.

Anyone:

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

Only one command can be requested per comment.

(automatically generated message, version: 1.32.7)

@jenkins-cert-app jenkins-cert-app added the security-audit-todo The security team needs to audit the hosting request code label Dec 24, 2024
Copy link

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.

  • ⛔ Required: The following usernames in 'Jenkins project users to have release permission' need to log into Jira: michael_baron (reports are re-synced hourly, wait to re-check for a bit after logging in)
  • ⛔ Required: The following usernames in 'Jenkins project users to have release permission' need to log into Artifactory: michael_baron (reports are re-synced hourly, wait to re-check for a bit after logging in)
  • ⛔ Required: The 'artifactId' from the pom.xml (p4sa-plugin) is incorrect, it should be p4sa ('New Repository Name' field with "-plugin" removed)
  • ⛔ Required: The <groupId> from the pom.xml should be io.jenkins.plugins instead of com.perforce

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

@jenkins-cert-app
Copy link
Collaborator

The Jenkins Security Scan discovered 3 finding(s) 🔍.

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.

Jenkins: Plaintext password storage

You can find detailed information about this finding here.

AnalysisBuilderPipelineConfig.java#13
Field should be reviewed whether it stores a password and is serialized to disk: validateApiToken
ValidateAPIConnector.java#26
Field should be reviewed whether it stores a password and is serialized to disk: ltoken

Jenkins: Generally unsafe method calls

You can find detailed information about this finding here.

ValidateAPIConnector.java#37
Potentially unsafe invocation of SSLContext#init
Potentially unsafe invocation of HttpsURLConnection#setSSLSocketFactory

@jenkins-cert-app jenkins-cert-app added security-audit-needs-correction The security audit revealed issues that must be corrected from the hosting request and removed security-audit-todo The security team needs to audit the hosting request code labels Dec 24, 2024
@mawinter69
Copy link
Contributor

@mawinter69
Copy link
Contributor

/hosting re-check

Copy link

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.

  • ⛔ Required: The following usernames in 'Jenkins project users to have release permission' need to log into Jira: michael_baron (reports are re-synced hourly, wait to re-check for a bit after logging in)
  • ⛔ Required: The following usernames in 'Jenkins project users to have release permission' need to log into Artifactory: michael_baron (reports are re-synced hourly, wait to re-check for a bit after logging in)
  • ⛔ Required: The 'artifactId' from the pom.xml (p4sa-plugin) is incorrect, it should be p4sa ('New Repository Name' field with "-plugin" removed)
  • ⛔ Required: The <groupId> from the pom.xml should be io.jenkins.plugins instead of com.perforce

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

@mawinter69
Copy link
Contributor

Do you have the image https://github.com/michael-baron/P4SA-Jenkins-Plugin/blob/master/src/main/webapp/icon/p4.png as svg? When you use your plugin with dark theme I think it will be hard to see the image

@mawinter69
Copy link
Contributor

Seems your repo in github is not indexed. Not sure what is causing this but it prevents some checks to run properly.

@timja
Copy link
Member

timja commented Dec 29, 2024

Seems your repo in github is not indexed. Not sure what is causing this but it prevents some checks to run properly.

Seems to be a few complaints here:
https://github.com/orgs/community/discussions/45538#discussioncomment-11109104

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hosting-request Request to host a component in jenkinsci needs-fix security-audit-needs-correction The security audit revealed issues that must be corrected from the hosting request
Projects
None yet
Development

No branches or pull requests

4 participants