Closed Bug 1303344 Opened 8 years ago Closed 8 years ago

Permission denied to access property

Categories

(Firefox :: Untriaged, defect)

48 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: joe.younkins, Unassigned, NeedInfo)

References

Details

(Keywords: site-compat, testcase-wanted)

Attachments

(1 file)

138.80 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document
Details
Attached file firefox_issue.docx
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:48.0) Gecko/20100101 Firefox/48.0 Build ID: 20160817112116 Steps to reproduce: In the previous versions of firefox the links below were working. Once we upgraded to version 48 we were unable to access the links. Using Firefox 48 we experience the following issue: 1. Login into our PeopleSoft Portal (domain is psportal.gatech.edu) 2. Navigate to Travel and expense (domain is psoft.gatech.edu) 3. Click on Create New Travel Auth. When hovering above the link the following is displayed: javascript:hAction_win0(document.win0,'GT_TE_INTRO_WRK_GT_TE_LINK1',%200,%200,%20'Create%20New%20Travel%20Auth',%20false,%20true); After clicking on the link the browser hangs/spins. The web console displays the following message: Error: Permission denied to access property "document" Actual results: Brower hangs/spins Expected results: The user should have been taken to the link that was clicked on.
Is it possible to attach a testcase? I guess the website is not public and you can't provide limited access? Maybe could you try to save locally the page, and load it in Firefox to check the issue is reproducible.
Flags: needinfo?(joe.younkins)
hello, Permission denied to access property might be because of the following reasons: -that Mozilla 48.0 version you were using might be having security bug that is why its not opening those URL. -that company might had started using proxy server without informing you. -as you upgraded Mozilla, company's URL you were trying to access might had in the process of upgrading their system. Thanks
(In reply to Loic from comment #1) > Is it possible to attach a testcase? I guess the website is not public and > you can't provide limited access? > > Maybe could you try to save locally the page, and load it in Firefox to > check the issue is reproducible. Hi Loic, The website requires a user id and pwd to access so unfortunately I cannot grant limited access. I did save the page locally and opened it in firefox and the issue was re-created.
So in that case, maybe you can only save the page and attach it to the bug report in a ZIP archive. You can eventually edit the source code to anonymize some private data.
Keywords: testcase-wanted
Hi, The error is probably due to violation of same-origin policy, element loaded from a different domain.The company's URL might not have been upgraded accordingly with the firefox version 48. Keywords:same-origin-policy Summary: Violation of same-origin policy
Flags: needinfo?(marcia)
Flags: needinfo?(joe.younkins)
Hi Joe, As we would need login info in order to be able to reproduce the issue and you are unable to provide it, and because you said this worked in previous versions on Firefox, could you please try to find a regression range using Mozregression tool? Information on the tool is available at http://mozilla.github.io/mozregression/. Please don't hesitate to contact us if you encounter any problems.
Flags: needinfo?(joe.younkins)
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
How could a bug that first appears in Firefox 48 possibly be a duplicate of an ESR10-only bug that was fixed 4 years ago?
Status: RESOLVED → REOPENED
Ever confirmed: true
Flags: needinfo?(tabs16w)
Resolution: DUPLICATE → ---
Something here is definitely weird: I can't think of any cases offhand in which the javascript: URL would _execute_ but not be able to get the bareword 'document' from its global. We run such urls with the origin of the global they're running against, if we run them at all.... Joe, if you do have a locally saved version that shows this problem, and are able to share it at all (either with one particular person, or by attaching to this bug), that would be incredibly helpful...
(In reply to Boris Zbarsky [:bz] (TPAC) from comment #8) > How could a bug that first appears in Firefox 48 possibly be a duplicate of > an ESR10-only bug that was fixed 4 years ago? The two bugs are of similar type
Flags: needinfo?(tabs16w)
See Also: → CVE-2012-3991
That's far too low a bar to mark something duplicate.
Keywords: site-compat
Guess this is a dup of Bug 1292522. Reporter: can you test the app with Firefox 49?
Flags: needinfo?(marcia)
Marking this as Resolved: Incomplete due to the lack of response from the reporter. If anyone can still reproduce it on latest versions, feel free to reopen the issue and provide more information.
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: