Closed
Bug 284577
Opened 20 years ago
Closed 11 years ago
sidebar.addPanel doesn't show user the URL they're bookmarking, could be used for spoofing
Categories
(Firefox :: Bookmarks & History, defect)
Firefox
Bookmarks & History
Tracking
()
VERIFIED
FIXED
Firefox 23
People
(Reporter: u115577, Unassigned)
References
Details
(Keywords: sec-want, testcase, Whiteboard: [sg:want])
Attachments
(1 file, 1 obsolete file)
(deleted),
text/html
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050302 Firefox/1.0+
"window.sidebar.addPanel" function allows you to bookmark any document as
bookmark panel. If an attacker could convince a user to bookmark an arbitrary
XPI file disguised as some useful site, this could be used to bypass XPI whitelist.
Reproducible: Always
Steps to Reproduce:
1. open testcase
2. click "Bookmark This Page..." and bookmark it
3. select "Some Useful Site" from bookmark
Actual Results:
XPI is loaded in the sidebar, whitelist is ignored and install dialog is shown
immediately.
Expected Results:
XPI is loaded in the sidebar, but whitelist blocks the installation and the
appropriate information bar is shown.
Mark this as Security-Sensitive Bug just like Bug 264560.
Comment 2•20 years ago
|
||
Nominating to block releases, and adding some people who could maybe help out.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.8b2?
Flags: blocking-aviary1.0.2?
Whiteboard: [sg:investigation]
Comment 3•20 years ago
|
||
Bypassing the whitelist is not a security problem requiring the confidential
flag, especially not one that requires convincing a user to bookmark an unknown
link.
The reason this bypasses the whitelist is because we explicitly remove referrer
information from bookmarks for privacy reasons. What reasonable referrer could
we use? We only know the user has bookmarked it and in that case we must assume
the user wanted it. It doesn't need to be a panel, any bookmark to a .xpi would
equally bypass the whitelist.
Group: security
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Whiteboard: [sg:investigation] → [sg:nse]
Updated•20 years ago
|
Flags: blocking1.8b2?
Flags: blocking1.8b2-
Flags: blocking-aviary1.0.3?
Flags: blocking-aviary1.0.3-
Comment 5•20 years ago
|
||
> Another testcase is here. How about this?
OK, got me there -- but that's really your bug 290079 isn't it? I guess that
depends on how mconnor fixes that one.
Status: RESOLVED → REOPENED
Depends on: 290079
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.0.3?
Flags: blocking-aviary1.0.3-
Resolution: WONTFIX → ---
Updated•20 years ago
|
Assignee: xpi-engine → dveditz
Status: REOPENED → NEW
Component: Installer: XPInstall Engine → Software Update
Flags: blocking1.8b2-
Product: Core → Firefox
Version: Trunk → 1.0 Branch
Updated•20 years ago
|
Flags: blocking-aviary1.1? → blocking-aviary1.1+
I'm testing 2005-04-13-00-aviary1.0.1. The patch proposed in Bug 290079 added
appropriate security check, but doesn't block XPI installation.
Keywords: testcase
Summary: sidebar bookmark panel allows bypassing of XPI whitelist → sidebar web panel allows bypassing of XPI whitelist
Updated•19 years ago
|
Flags: blocking-aviary1.1+ → blocking-aviary1.1-
If the whitelist is bypassed easily, some kind of attack can be done
successfully on Firefox. This bug contains potential hazards such as bug 293331.
Also see MFSA 2005-42:
http://www.mozilla.org/security/announce/mfsa2005-42.html
Firefox is more secure than Mozilla Suite? Nope.
Nominate for 1.1 again.
Flags: blocking-aviary1.1- → blocking-aviary1.1?
Comment 10•19 years ago
|
||
The whitelist solely allows the site to present an install dialog. How is this
exploitable in a way that a whitelisted site can't exploit someone? Or is this
just a defence in depth case, where future attacks against the dialog can be
somehow mitigated here?
Flags: blocking-aviary1.1? → blocking1.8b4?
Comment 11•19 years ago
|
||
If you ask me, the risks of whitelist bypassing is dwarfed by the horrendously
bad ideas demonstrated by your testcases of 1) having the addPanel() dialog not
show the URL being bookmarked and 2) letting any site anywhere at any time open
or replace your sidebar using target=_search. Especially the latter.
Updated•19 years ago
|
Flags: blocking1.8b4? → blocking1.8b4-
Updated•18 years ago
|
QA Contact: software.update
->EM
Component: Software Update → Extension/Theme Manager
Updated•18 years ago
|
QA Contact: software.update → extension.manager
Comment 13•18 years ago
|
||
The EM doesn't use the whitelist... xpinstall uses it and if it satisfies the whitelist requirement cpinstall opens the xpinstall dialog.
Still though, this works in the main content area just fine and it doesn't work in the sidebar's content area. I don't see a component appropriate for the sidebar in Firefox so Firefox -> General
Component: Extension/Theme Manager → General
Comment 14•15 years ago
|
||
Comment on attachment 180497 [details]
testcase 2
The "_search" target doesn't work anymore
Attachment #180497 -
Attachment is obsolete: true
Updated•15 years ago
|
Assignee: dveditz → nobody
Component: General → Bookmarks & History
QA Contact: general → bookmarks
Summary: sidebar web panel allows bypassing of XPI whitelist → sidebar.addPanel doesn't show user the URL they're bookmarking, could be used for spoofing
Whiteboard: [sg:nse] → [sg:want]
Version: 1.0 Branch → unspecified
Comment 15•15 years ago
|
||
Yeah, we removed it in bug 438526.
Comment 16•15 years ago
|
||
Give me a couple more years, and the story will be that I removed it because of things like this ;)
Comment 17•15 years ago
|
||
if i'm not wrong, actual Add Bookmarks panel shows the location when it is called through sidebar.AddPanel()
Comment 18•11 years ago
|
||
Bug 691647 removed addPanel.
Status: NEW → RESOLVED
Closed: 20 years ago → 11 years ago
Resolution: --- → INVALID
Updated•11 years ago
|
Updated•11 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•