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

Report the use of components with vulnerabilities in argo-cd #18139

Closed
HouqiyuA opened this issue May 9, 2024 · 1 comment
Closed

Report the use of components with vulnerabilities in argo-cd #18139

HouqiyuA opened this issue May 9, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@HouqiyuA
Copy link

HouqiyuA commented May 9, 2024

Dear Team Members:
Greetings! Our team is very interested in your project. we performed source code perspective security analysis (SCA) and vulnerability library association analysis on this project and found that components with vulnerabilities are still being used into this project.We would like to report this issue to you,so that you can fix and improve it accordingly. I add the details in json file below. Please confirm whether this problem really exists and confirm with us. Looking forward to hearing from you and discussing more details with us, thank you very much for your time and attention.

Note: Each "affect_components" field in the report represents the vulnerable component introduced by this project. The other is the vulnerability information associated with it.

Qiyu Hou

argo-cd-master_report.json

@HouqiyuA HouqiyuA added the bug Something isn't working label May 9, 2024
@crenshaw-dev
Copy link
Collaborator

Hi! Analyzing security scanner output and remediating each reported vulnerability is beyond what the Argo CD team can provide.

We run our own Snyk scans weekly and target remediating any Critical or High severity vulnerabilities in the currently-supported release range.

If you would like to request that a certain dependency vulnerability be resolved, please report it as its own issue along with the severity according to Snyk and the affected Argo CD version(s) (if they are in the currently supported version range).

If Snyk evaluates the vulnerability to be less than High severity, and you would still like the vulnerability to be remediated, please provide an explanation of why the vulnerability poses a real (and not just theoretical) threat to users.

Finally, pull requests are appreciated and will likely be addressed more quickly than issues.

@crenshaw-dev crenshaw-dev closed this as not planned Won't fix, can't repro, duplicate, stale May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants