Closed
Bug 1254226
Opened 10 years ago
Closed 10 years ago
XSS through javascript: callback URLs in auth delegation
Categories
(Bugzilla :: User Accounts, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 6.0
People
(Reporter: jwkbugzilla, Assigned: LpSolit)
References
Details
(Keywords: reporter-external, sec-moderate, wsec-xss, Whiteboard: XSS if user clicks on explicit javascript: link on confirmation page)
Attachments
(1 file)
|
1.24 KB,
patch
|
dylan
:
review+
|
Details | Diff | Splinter Review |
This issue can be reproduced if the Bugzilla instance has auth delegation enabled, consider the following link for example:
> https://bugzilla.mozilla.org/auth.cgi?callback=javascript:alert%28/xss/%29&description=foobar
Clicking the link will produce a message saying "xss." The issue is not too critical because the link title gives it away and obfuscation possibilities are limited, still a vulnerability however. Vanilla Bugzilla instances are affected as well, landfill.bugzilla.org doesn't have auth.cgi however.
Note that auth.cgi only allows HTTP and HTTPS as callbacks, the corresponding check only happens when confirming delegation however.
| Assignee | ||
Comment 1•10 years ago
|
||
Hum, where do you see the "xss" message? Clicking this link generates a page with:
A third-party website (javascript:alert(/xss/)) would like to have complete access to your Bugzilla account.
The description of the site reads:
foobar
Do you want this website to have complete access to your Bugzilla account?
But no alert() is triggered.
| Reporter | ||
Comment 2•10 years ago
|
||
The alert is produced if you click the website link on this page.
| Assignee | ||
Comment 3•10 years ago
|
||
| Assignee | ||
Updated•10 years ago
|
Severity: normal → minor
Target Milestone: --- → Bugzilla 6.0
Updated•10 years ago
|
Flags: sec-bounty?
Comment 4•10 years ago
|
||
Comment on attachment 8727580 [details] [diff] [review]
patch, v1
Review of attachment 8727580 [details] [diff] [review]:
-----------------------------------------------------------------
r=dylan
Attachment #8727580 -
Flags: review?(dkl) → review+
| Assignee | ||
Comment 5•10 years ago
|
||
Why is this bug tagged sec-high? Not only must the victim first load a page such as the one described in comment 0, but then the victim must also click the URL displayed in that page to trigger XSS. So it requires two actions from the user. Being an authentication page, I doubt one would click on a link asking for full access to your account when the website name is "javascript:alert(/xss/)". XSS is not triggered when loading the initial page; only when clicking on the "javascript:alert(/xss/)" link.
FYI, there is no Bugzilla release with that code yet as it's in master only.
| Reporter | ||
Comment 6•10 years ago
|
||
(In reply to Frédéric Buclin from comment #5)
> FYI, there is no Bugzilla release with that code yet as it's in master only.
Seems to be correct but BMO is using this already. The rest - not up to me.
Updated•10 years ago
|
Keywords: sec-high → sec-moderate
Whiteboard: XSS if user clicks on explicit javascript: link on confirmation page
| Assignee | ||
Comment 7•10 years ago
|
||
To ssh://gitolite3@git.mozilla.org/bugzilla/bugzilla.git
c7e8031..3368986 master -> master
Group: bugzilla-security
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Flags: sec-bounty? → sec-bounty+
Updated•2 years ago
|
Keywords: reporter-external
You need to log in
before you can comment on or make changes to this bug.
Description
•