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

Test Snyk CircleCi Build on Repository #2

Open
2 tasks
bama4 opened this issue Feb 15, 2021 · 4 comments
Open
2 tasks

Test Snyk CircleCi Build on Repository #2

bama4 opened this issue Feb 15, 2021 · 4 comments
Assignees
Labels

Comments

@bama4
Copy link
Contributor

bama4 commented Feb 15, 2021

Describe the issue as a Story
As a developer of Govready, I wish to run Snyk io on each push to determine any potential vulnerabilities.
I also wish to have reports of vulnerabilities in dependencies.

To Reproduce
N/A

Expected behavior
At each pull request/push, the CircleCi build for Snyk io is executed to report vulnerabilities with the requirements.txt file.
I can also see reports in the Snyk Organization Account.
Screenshots
N/A

Desktop (please complete the following information):
N/A

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]
  • Virtual Machine?
  • Screen size

Developer hints

N/A

Acceptance criteria

GIVEN a vulnerability in the dependencies of the repository
WHEN I push up code/create a pull request
THEN snyk io should create pull requests to address the vulnerabilities

  • GovReady Account needs to be set up for Snyk with API token changed to Govready Account Snyk API token.
  • GovReady Project in Snyk needs to be specified as the project in the CircleCi Build snyk-scan parameters.

Additional context
CircleCi Instructions: https://circleci.com/developer/orbs/orb/snyk/snyk

Links referenced in issue

@bama4 bama4 self-assigned this Feb 15, 2021
@bama4 bama4 added the security label Feb 15, 2021
bama4 added a commit that referenced this issue Feb 15, 2021
bama4 added a commit that referenced this issue Feb 15, 2021
bama4 added a commit that referenced this issue Feb 15, 2021
bama4 added a commit that referenced this issue Feb 15, 2021
bama4 added a commit that referenced this issue Feb 15, 2021
bama4 added a commit that referenced this issue Feb 15, 2021
bama4 added a commit that referenced this issue Feb 15, 2021
bama4 added a commit that referenced this issue Feb 16, 2021
bama4 added a commit that referenced this issue Feb 16, 2021
bama4 added a commit that referenced this issue Feb 16, 2021
bama4 added a commit that referenced this issue Feb 16, 2021
@bama4
Copy link
Contributor Author

bama4 commented Feb 16, 2021

Snyk Build Failure Example

Sample_Snyk_Build_Failure

@bama4
Copy link
Contributor Author

bama4 commented Feb 16, 2021

Example Snyk Report Finding

jinja2_example_vulnerability

@bama4
Copy link
Contributor Author

bama4 commented Feb 16, 2021

Example Snyk Proof of Concept

https://snyk.io/vuln/SNYK-PYTHON-JINJA2-1012994

jinja_PoC

@bama4
Copy link
Contributor Author

bama4 commented Feb 16, 2021

Snyk Vulnerability Database Search

https://snyk.io/vuln

Snyk_database

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant