Closed
Bug 600271
Opened 15 years ago
Closed 15 years ago
Remove oauth_token and oauth_verifier from URL
Categories
(support.mozilla.org :: Army of Awesome, task)
support.mozilla.org
Army of Awesome
Tracking
(Not tracked)
VERIFIED
FIXED
2.2.5
People
(Reporter: mcoates, Unassigned)
References
Details
(Whiteboard: [infrasec:cookie])
Issue
After twitter authentication the user is redirected back to the customer care page along with the oauth_token and oath_verifier values in the URL as arguments. (token values shortened in example)
Example:
https://master.support.mozilla.com/en-US/army-of-awesome?twitter_auth_request=1&oauth_token=aBUV0cT&oauth_verifier=fXKoOZ8
This communication is over HTTPS and there is no concern of malicious interception of this data. However, users often copy and paste URLs to share a page with others. This could inadvertently disclose the two pieces of data that could be used to assist an attacker.
Recommended Remediation
1. First investigate if it is possible to instruct twitter to send this data back via POST parameters or header values.
2. If option 1 is not possible then modify the application to automatically redirect the user back to a "clean" url that does not contain the token values. This still exposes the token values within the browser history, but mitigates the primary concern of inadvertent "copy and paste" disclosure.
Updated•15 years ago
|
Target Milestone: --- → 2.2.5
Comment 1•15 years ago
|
||
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 2•15 years ago
|
||
Verified fixed on https://master.support.mozilla.com. Marking verified.
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Group: websites-security
You need to log in
before you can comment on or make changes to this bug.
Description
•