Skip to content

Conversation

@dobsonj
Copy link
Member

@dobsonj dobsonj commented Jan 18, 2024

Ignore these two snyk errors. One is a hardcoded secret used in a unit test and nowhere else (it's not a real secret), the other is a complaint about the e2eprovider removing an existing socket before it creates a socket at that same path. Nothing in the core driver that runs on real clusters.

 ✗ [Low] Hardcoded Secret
   ID: cf46edb3-d35f-4887-855d-6ba6d11abeee 
   Path: pkg/util/secretutil/secret_test.go, line 104 
   Info: Avoid hardcoding values that are meant to be secret. Found a hardcoded string used in keyPEM.
 ✗ [Low] Path Traversal
   ID: 9ad47a1a-2143-4d4f-b0fb-88ea459987f9 
   Path: test/e2eprovider/e2e_provider.go, line 54 
   Info: Unsanitized input from a CLI argument flows into os.Remove, where it is used as a path. This may result in a Path Traversal vulnerability and allow an attacker to delete arbitrary files.

from https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/47618/rehearse-47618-pull-ci-openshift-secrets-store-csi-driver-main-security/1745954190951190528

/cc @openshift/storage

@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jan 18, 2024
@openshift-ci-robot
Copy link

@dobsonj: This pull request references Jira Issue OCPBUGS-27242, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Ignore these two snyk errors. One is a hardcoded secret used in a unit test and nowhere else (it's not a real secret), the other is a complaint about the e2eprovider removing an existing socket before it creates a socket at that same path. Nothing in the core driver that runs on real clusters.

✗ [Low] Hardcoded Secret
  ID: cf46edb3-d35f-4887-855d-6ba6d11abeee 
  Path: pkg/util/secretutil/secret_test.go, line 104 
  Info: Avoid hardcoding values that are meant to be secret. Found a hardcoded string used in keyPEM.
✗ [Low] Path Traversal
  ID: 9ad47a1a-2143-4d4f-b0fb-88ea459987f9 
  Path: test/e2eprovider/e2e_provider.go, line 54 
  Info: Unsanitized input from a CLI argument flows into os.Remove, where it is used as a path. This may result in a Path Traversal vulnerability and allow an attacker to delete arbitrary files.

from https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/47618/rehearse-47618-pull-ci-openshift-secrets-store-csi-driver-main-security/1745954190951190528

/cc @openshift/storage

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link

openshift-ci bot commented Jan 18, 2024

@dobsonj: GitHub didn't allow me to request PR reviews from the following users: openshift/storage.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

Ignore these two snyk errors. One is a hardcoded secret used in a unit test and nowhere else (it's not a real secret), the other is a complaint about the e2eprovider removing an existing socket before it creates a socket at that same path. Nothing in the core driver that runs on real clusters.

✗ [Low] Hardcoded Secret
  ID: cf46edb3-d35f-4887-855d-6ba6d11abeee 
  Path: pkg/util/secretutil/secret_test.go, line 104 
  Info: Avoid hardcoding values that are meant to be secret. Found a hardcoded string used in keyPEM.
✗ [Low] Path Traversal
  ID: 9ad47a1a-2143-4d4f-b0fb-88ea459987f9 
  Path: test/e2eprovider/e2e_provider.go, line 54 
  Info: Unsanitized input from a CLI argument flows into os.Remove, where it is used as a path. This may result in a Path Traversal vulnerability and allow an attacker to delete arbitrary files.

from https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/47618/rehearse-47618-pull-ci-openshift-secrets-store-csi-driver-main-security/1745954190951190528

/cc @openshift/storage

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 18, 2024
@openshift-ci
Copy link

openshift-ci bot commented Jan 18, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dobsonj

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 18, 2024
@openshift-ci
Copy link

openshift-ci bot commented Jan 18, 2024

@dobsonj: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jsafrane
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 19, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit d169ab3 into openshift:main Jan 19, 2024
@openshift-ci-robot
Copy link

@dobsonj: Jira Issue OCPBUGS-27242: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-27242 has not been moved to the MODIFIED state.

Details

In response to this:

Ignore these two snyk errors. One is a hardcoded secret used in a unit test and nowhere else (it's not a real secret), the other is a complaint about the e2eprovider removing an existing socket before it creates a socket at that same path. Nothing in the core driver that runs on real clusters.

✗ [Low] Hardcoded Secret
  ID: cf46edb3-d35f-4887-855d-6ba6d11abeee 
  Path: pkg/util/secretutil/secret_test.go, line 104 
  Info: Avoid hardcoding values that are meant to be secret. Found a hardcoded string used in keyPEM.
✗ [Low] Path Traversal
  ID: 9ad47a1a-2143-4d4f-b0fb-88ea459987f9 
  Path: test/e2eprovider/e2e_provider.go, line 54 
  Info: Unsanitized input from a CLI argument flows into os.Remove, where it is used as a path. This may result in a Path Traversal vulnerability and allow an attacker to delete arbitrary files.

from https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/47618/rehearse-47618-pull-ci-openshift-secrets-store-csi-driver-main-security/1745954190951190528

/cc @openshift/storage

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-robot
Copy link

Fix included in accepted release 4.16.0-0.nightly-2024-01-21-092529

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants