FireFox Updater

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

FireFox Updater

L4 Transporter

We have a policy which allows Firefox to only run normally (Allow in the New UI terms). This means it can't elevate and Firefox runs fine that way (we actually have the same with all the various browsers). We are seeing that when the updater runs it appears to work fine, but we get two Elevation Requests in the Events Management queue from it (they automatically occur, users are not manually doing it). The two elevation requests are both for regsvr32.exe, each has one of the below arguments:

/s "C:\Program Files\Mozilla Firefox\AccessibleMarshal.dll"

/s "C:\Program Files\Mozilla Firefox\AccessibleHandler.dll"

 

So it appears that the updater is trying to register the updated DLLs. Since there is an Elevation Request, I assume it's not working, but the update appears to have been successful and Firefox continues to run fine.

 

Anyone else seeing or have seen this? If so, what did you do?

 

I considered creating a Trust policy for the Software updater (Firefox updater is a predefined one), but I noticed the permission it gives it is Allow (not Elevate) so I'm not sure if that will work properly either. Anyone have an insight into why some of the Trust policies only use Allow, not Elevate if needed (the SCCM one is the same, just Allow)?

 

Thanks in advance for any help!

5 REPLIES 5

L4 Transporter

Anyone have any information on this? Does anyone have a Trusted Updater policy in use for the FireFox updater?

L3 Networker

Hi @Ron Martin​ 

 

In the old UI, in the trusted Updater/Distributer policies only, you could set all or specific installed applications to be handled differently than the installer itself, e.g. to run elevated when installer is only allowed to run normally, and vice-versa. Updater/Installer’s child processes, what seems to be the case here, had the same “hardcoded” permission as their father process, and this was enforced exclusively, e.g. overriding higher-priority advanced application policies.

 

In the new UI we preserved the same logic for the child processes, and we applied user-chosen action to all or none installed applications.

L4 Transporter

Hi Albert,

 

Thanks for this information. However, how does CyberArk reconcile this choice with the fact that the Firefox updater has a child process that requires elevation? This is not specific to a single customer, but rather to all users of Firefox and EPM. And since this is a pre-defined updater, shouldn't it be coded to work properly with what it is updating? I'm just confused about why this updater is set the way it is when it doesn't work that way.

 

Thanks.

Choosing to elevate an application's child processes is the EPM admins' choice/decision. Cyberark's predefined policy only set the base settings for application whitelisting. From what I understand about the situation, firefox is working properly without the need to elevate those two child processes mentioned.

 

Feel free to correct me, we are all learning together 🙂

The elevated portion of the updater is registering two DLLs that have to do with Firefox accessibility functions. If you don't use those, Firefox does indeed work fine without this elevation. But I suspect (haven't tried it) there is some accessibility functionality there that will not work because they didn't register. Either that, or Firefox itself has a bad updater. 🙂

 

In our EPM setup if something tries to elevate we get an entry in Events Management so we can handle it. So each time the updater runs for one of our thousands of users we get two entries (one for each DLL it tries to register). Even if Firefox is working fine for the users, that's annoying to the admins. So we simply created our own Elevate if necessary advanced policy for the updater instead. Hence, our problem is resolved.

 

I raised this discussion because I wanted to let CyberArk know that their predefined updater for Firefox didn't actually match the needs of the updater.

 

PS. Firefox itself does not need elevation (we have Firefox in an Allow policy), just the updater for those two DLL registrations.

  • 482 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!