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 kubeedge #5596

Open
HouqiyuA opened this issue May 8, 2024 · 1 comment
Open

Report the use of components with vulnerabilities in kubeedge #5596

HouqiyuA opened this issue May 8, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@HouqiyuA
Copy link

HouqiyuA commented May 8, 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

kubeedge-master_report.json

@HouqiyuA HouqiyuA added the kind/bug Categorizes issue or PR as related to a bug. label May 8, 2024
@Shelley-BaoYue
Copy link
Collaborator

Hi, @HouqiyuA Thanks for raising these questions and we will address them asap. Btw, Security issues can be reported to our security team as https://github.com/kubeedge/kubeedge?tab=readme-ov-file#reporting-security-vulnerabilities

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants