Closed
Bug 1256412
Opened 10 years ago
Closed 9 years ago
uninstall.exe from the mozilla maintenance service does not have a valid digital signature
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: patchwerk.git, Assigned: molly)
Details
(Whiteboard: [fce-active-legacy])
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160303134406
Steps to reproduce:
Install Firefox 44 from: https://ftp.mozilla.org/pub/firefox/releases/44.0/win64/en-US/
Navigate to ~\Program Files (x86)\Mozilla Maintenance Service\
Verify [Uninstall.exe] does not have a Digital Signature.
Actual results:
File does not appear to originate from Mozilla.org as it is not Digitally signed as other Firefox files.
Expected results:
File should be digitally signed as proof it is authentic.
| Reporter | ||
Updated•10 years ago
|
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Comment 1•10 years ago
|
||
Benjamin, who could look at this in rstrong's absence?
Group: firefox-core-security → toolkit-core-security
Component: Untriaged → Application Update
Flags: needinfo?(benjamin)
Product: Firefox → Toolkit
Summary: Unsigned PE present, Uninstall.exe → uninstall.exe from the mozilla maintenance service does not have a valid digital signature
Comment 2•10 years ago
|
||
->mhowell, although it's possible this is something in releng signing
Assignee: nobody → mhowell
Flags: needinfo?(benjamin)
Comment 3•10 years ago
|
||
Also unless there is evidence that this will result in a security exploit, we should open this up.
| Assignee | ||
Comment 4•10 years ago
|
||
Can't blame RelEng for this one; the file isn't signed because it's generated by NSIS during installation of the service, not created at build time. This is standard practice for simple NSIS installers.
In my opinion this is not something we need to fix. The file can only be created inside Program Files, where it can only be written to by users with administrative privileges. Also, the installer that creates this file *is* signed. Those two facts combined mean that tampering with the code would be very difficult and probably not worthwhile for creating an exploit.
The only real defect is that the UAC prompt when you run the uninstaller says "Publisher: Unknown," and that in and of itself is not a security defect. It's not even a very serious cosmetic defect, because the maintenance service uninstaller is intended to be run indirectly by the uninstaller for the main product, and in that case that prompt is not shown.
| Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Matt Howell [:mhowell] from comment #4)
> Can't blame RelEng for this one; the file isn't signed because it's
> generated by NSIS during installation of the service, not created at build
> time. This is standard practice for simple NSIS installers.
>
> In my opinion this is not something we need to fix. The file can only be
> created inside Program Files, where it can only be written to by users with
> administrative privileges. Also, the installer that creates this file *is*
> signed. Those two facts combined mean that tampering with the code would be
> very difficult and probably not worthwhile for creating an exploit.
> The only real defect is that the UAC prompt when you run the uninstaller
> says "Publisher: Unknown," and that in and of itself is not a security
> defect. It's not even a very serious cosmetic defect, because the
> maintenance service uninstaller is intended to be run indirectly by the
> uninstaller for the main product, and in that case that prompt is not shown.
Thank you for the explanation of why it wasn't signed.
Updated•10 years ago
|
Group: toolkit-core-security
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•9 years ago
|
Whiteboard: [fce-active]
Updated•8 years ago
|
Whiteboard: [fce-active] → [fce-active-legacy]
You need to log in
before you can comment on or make changes to this bug.
Description
•