Page MenuHomePhabricator

Fix a CSRF issue with adding new email addresses
ClosedPublic

Authored by epriestley on Jun 30 2016, 3:25 PM.
Tags
None
Referenced Files
F18993319: D16200.diff
Wed, Nov 19, 7:45 AM
F18830103: D16200.id.diff
Sat, Oct 25, 4:12 AM
F18827453: D16200.diff
Fri, Oct 24, 10:09 AM
F18779385: D16200.id.diff
Oct 11 2025, 1:43 PM
F18774242: D16200.id38965.diff
Oct 9 2025, 6:05 PM
F18733381: D16200.id.diff
Sep 30 2025, 10:33 PM
F18619547: D16200.id38964.diff
Sep 15 2025, 2:46 AM
F18528154: D16200.id38964.diff
Sep 6 2025, 8:12 PM
Subscribers
None

Details

Summary

The first dialog was being given the wrong user ($user, should be $viewer), leading to a CSRF issue.

(The CSRF token it generated was invalid in all validation contexts, so this wasn't a security problem or a way to capture CSRF tokens for other users.)

Use newDialog() instead.

(This seems completely unrelated to the vaguely-similar-looking issues we saw earlier this week.)

Test Plan
  • Added a new email address.
  • Clicked "Done" on the last step.
  • Completed workflow instead of getting a CSRF error.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Fix a CSRF issue with adding new email addresses.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
tide added a reviewer: tide.
This revision is now accepted and ready to land.Jun 30 2016, 3:31 PM
This revision was automatically updated to reflect the committed changes.