-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Nominations Closed] Jenkins Security MVP 2025 🏆 #7980
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
Comments
I would like to nominate @yaroslavafenkin for his work on the CSP project. Yaroslav provided tons of work and insights into the project and how Jenkins' CSP can be enhanced. This work helped not only Jenkins core, but its plugin ecosystem as well. This was lot of work done in a somewhat short amount of time, yielding fantastic results. |
I would also like to nominate @shlomomdahan for his work on the CSP project. Shlomo contributed his time and effort to help enhance the Jenkins CSP and provided support for both Jenkins core and the plugin ecosystem. These efforts are crucial in ensuring that Jenkins is both secure and future proof. The work done in this project also helped educate and inform plugin maintainers about what is needed when it comes time to provide further safe-guarding in the future. |
I am nominating Chenwei Jiang and Yue Yang for their excellent report of SECURITY-3430 / CVE-2024-43044 to the Jenkins project. This vulnerability allows attacking Jenkins controllers through its core CI use case. It was the most severe vulnerability since the previous nomination period. Being in the rather arcane Remoting library underlying the communication between agents and controllers, it was also the most interesting! (In case this award cannot be presented to a group of people: Chenwei Jiang is the primary reporter.) |
I nominate Daniel Beck for his skilled and thorough efforts to maintain and improve the security of Jenkins. His code reviews for Jenkins core are great examples of attention to detail and awareness of impact. He reviews security threats carefully and keeps himself current on recent security topics. He works well with release leads when delivering Jenkins security releases and works well with the Jenkins infrastructure team in many different areas. |
Uh oh!
There was an error while loading. Please reload this page.
This issue is to receive nominations for the Jenkins Security MVP 2025. This award is presented to an individual most consistently providing excellent security reports or resolving security issues.
To nominate someone, reply to this issue with the following:
Full name of the person you’re nominating
A short description of their contributions to Jenkins and why they should win.
Nomination Deadline: April 14, 2025
Please note: Last year's winner, Yaniv Nizry, cannot win the award for Jenkins Security MVP again this year.
Voting will be open from April 22 to June 5.
Winners will be announced at cdCon 2025, June 23–25.
More details are available HERE.
Award type:
The awards will be virtual credly badges again this year (not physical).
The text was updated successfully, but these errors were encountered: