-
Notifications
You must be signed in to change notification settings - Fork 100
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
Fix CVE-2022-27204 / SECURITY-1350 #39
Conversation
Implement suggestion from https://www.jenkins.io/doc/developer/security/form-validation/
Locally, GET does not work anymore:
And POST is CSRF protected:
|
@vimil Hi! What do you think about this pr? |
@vimil any progress here, it would be great if this fix is merged |
Pinging more members who could have write access |
Pretty please? What can we do to move this along? |
+1 |
Note: You can download my fixed version from CI: |
@ciis0 Hi, I am using your fixed version and the warning keeps to pop up. So, I would like to know when you can merge the new version? Does we need waiting more time? It is important because, I am using it in some workflows.... |
Hi @seam33, ciis0 does not have the permission to merge the PR, that needs to be done by an official Jenkins maintainer, but we could not get the attention of one yet. As such we'll need more patience. |
This fix looks incomplete, it only addresses the CSRF issue, not the missing permission checks. Regarding getting a new release with security issues being fixed when maintainers are unresponsive, see https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/ |
For CVE-2022-27204 the fix is complete (perm check is 05), only for SECURITY-1350 it is incomplete. I consider the CSRF more severe and easy to fix, while the perm check is not as severe and not as easy to fix. I will have a look at adopting the plugin. |
Good point. We'd still leave the security warning up even if this is addressed, because there's only one advisory entry and warning for both CVEs.
Depends on your setup, if you were an admin of ci.jenkins.io you'd see this differently :) |
https://www.jenkins.io/security/advisory/2022-03-15/#SECURITY-1350
Implement suggestion from https://www.jenkins.io/doc/developer/security/form-validation/
Fix CVE from title by applying suggestions from https://www.jenkins.io/doc/developer/security/form-validation/.