Page MenuHomePhabricator

Require a CSRF code for Twitter and JIRA (OAuth 1) logins
ClosedPublic

Authored by epriestley on Feb 23 2014, 11:19 PM.
Tags
None
Referenced Files
F15418532: D8318.id19783.diff
Thu, Mar 20, 11:52 PM
F15416384: D8318.diff
Thu, Mar 20, 10:49 AM
F15414215: D8318.id.diff
Wed, Mar 19, 11:27 PM
F15406007: D8318.diff
Tue, Mar 18, 12:03 PM
Unknown Object (File)
Feb 16 2025, 12:25 AM
Unknown Object (File)
Feb 9 2025, 11:37 AM
Unknown Object (File)
Feb 9 2025, 11:37 AM
Unknown Object (File)
Feb 9 2025, 11:37 AM
Subscribers

Details

Summary

OAuth1 doesn't have anything like the state parameter, and I overlooked that we need to shove one in there somewhere. Append it to the callback URI. This functions like state in OAuth2.

Without this, an attacker can trick a user into logging into Phabricator with an account the attacker controls.

Test Plan
  • Logged in with JIRA.
  • Logged in with Twitter.
  • Logged in with Facebook (an OAuth2 provider).
  • Linked a Twitter account.
  • Linked a Facebook account.
  • Jiggered codes in URIs and verified that I got the exceptions I expected.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

epriestley updated this revision to Unknown Object (????).Feb 23 2014, 11:20 PM
  • Restore the check for an empty 'code' parameter for OAuth2.