-
-
Notifications
You must be signed in to change notification settings - Fork 799
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
Security Audit of WINS form on static site #4588
Comments
This comment was marked as resolved.
This comment was marked as resolved.
@ExperimentsInHonesty I mentioned at our last meeting, that I think there is a security problem with the method used by the custom form; in particular, the form exposes a the URL of an HTTP endpoint which malicious actors could use to populate the response sheet with corrupt data. But I wonder if we should move forward with this issue anyway, so that we have another opinion that is formally documented in a DR. In the issue I mentioned that if the Wiki is not ready for editing, the dev should follow Jessica's interim instructions in "How to Contribute to the Wiki" for posting a comment here in the issue and then simply copying a link to the comment into the list Jessica created. |
@roslynwythe As per the discussion in the 2023-05-08 Dev/PM meeting, change this issue to just write the decision record and you can go ahead and write the decision record in a comment below in this issue. |
@JessicaLucindaCheng ok thanks. I've updated the issue Availability: 5/9 9 - midnight, 5/10 10-4 pm |
DR: Adopt the internal "Share your Wins" form in place of the current Google Form This is a record in the Decision Records on Solutions Not Implemented. IssueProblem StatementDrawbacks of the current Google Form include:
Potential SolutionA new "share your Wins" form has been developed which stores response data by sending an HTTP GET request to a web app which is bound to a Google Sheet. The request does not require credentials or API key, however the web app endpoint URL is exposed and could be targeted by malicious actors. At this time, Google does not provide a means for web apps to whitelist or examine the IP address of incoming requests, in order to protect against use by unauthorized clients. Feasibility DeterminationAdoption of the new form solution is not feasible, because the web app URL is exposed, and currently Google does not provide a means to whitelist specific IP addresses. |
Update:
|
Overview
As developers we must perform a security audit of the new HTML/JS implementation of the WINS form, in order to determine if use of the form exposes any secrets or exposes any resources to malicious actions.
Details
Action Items
Resources
The text was updated successfully, but these errors were encountered: